OMNO

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

Open OMNO in the provider directory and press Connect at OMNO Provider Overview page in the New connection section.

Step 2 - Fill in fields and select settings

• Client ID
• Client secret
• Currency / Features -> choose values available for your account (USD)

First request to Corefy API (MIN)

What it does: creates a payment-invoice; card data itself is collected and submitted separately by Corefy's checkout/SDK layer, not as part of this request. CVV is always required (no CVV-exempt mode), and 3D Secure control version is not configurable for this connector.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "b0818fe6-4526-4402-b08a-f71093a492f4",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "33333"
      }
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "a16162b7-7877-402c-877d-240f60bcbcf2",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "d95e408e-fcc3-4bce-8cfe-9c1b4369ae35",
        "name": "John Wick",
        "email": "johnwick@example.com",
        "phone": "+380123456789",
        "address": {
          "full_address": "Main street 1",
          "country": "FR",
          "city": "Paris",
          "region": "Paris",
          "post_code": "75001"
        }
      }
    }
  }
}

Extended request (MAX)

Why add extra fields (typical reasons): - Provide additional customer details for compliance/reconciliation - Positively influence conversion rate - Include optional fields required by your specific flow

Constants (fallback fields)

Constants are static values that Corefy can send to the provider instead of dynamic data from your API request, when those fields are missing in the request.

Priority (predictable rule): 1. If a value is present in the request -> Corefy uses the request value 2. Else if the constant is set -> Corefy uses the constant 3. Else -> provider may reject the request or apply its defaults (depends on provider)

Currently available constants (constant -> Corefy API field)

• FIRST_NAME -> customer.name (first name part)
• LAST_NAME -> customer.name (last name part)
• EMAIL -> customer.email
• PHONE -> customer.phone
• COUNTRY -> customer.address.country
• STATE -> customer.address.region (US/CA only)
• CITY -> customer.address.city
• ADDRESS -> customer.address.full_address
• POST_CODE -> customer.address.post_code

Refunds

OMNO does not support refunds.