UniversePay

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

Open UniversePay in the provider directory and press Connect at UniversePay Provider Overview page in the New connection section. Choose H2H Merchant account.

Step 2 - Fill in fields and select settings

• Shop ID
• Public Key
• Secret Key
• Test Mode -> (enable if you are using sandbox credentials)
• 3DS Mode
• Provider URL

Choose Currency / Features; check with your Corefy account manager which are enabled for your account.

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. UniversePay may return a 3D Secure challenge redirect depending on the card and your 3DS Mode setting; non-CVV sales are supported.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

This connector also supports USD, AZN, UAH, CZK, PLN, UZS.

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com",
        "address": {
          "country": "FR",
          "region": "IDF",
          "city": "Paris",
          "full_address": "1 Main street",
          "post_code": "75000"
        }
      }
    }
  }
}

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

Options

• ignore_callback -> optional, boolean - for cascading to work correctly, excludes finalizing the payment from the asynchronous callback; Corefy then relies only on an active status request (reconciliation) to finalize it.
• send_customer_data -> optional, boolean - off by default - enables sending customer address data (country/region/city/post code/address) to UniversePay at all; see the important note above.
• remove_space_from_initials -> optional, boolean - if the cardholder name consists of two single-letter initials and a surname (e.g. "J D Smith"), removes the space between the initials before sending it to UniversePay (e.g. "JD Smith").

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 - and only when send_customer_data is enabled.

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 -> a hardcoded placeholder is used (see the important note below)

Currently available constants (constant -> Corefy API field)

• IP -> customer's IP address
• DESCRIPTION -> the payment's description sent to UniversePay
• LANG -> language of UniversePay-side communication
• EMAIL -> customer.email
• REASON -> the reason text sent with a refund
• COUNTRY -> customer.address.country
• CITY -> customer.address.city
• STATE -> customer.address.region
• ZIP -> customer.address.post_code
• ADDRESS -> customer.address.full_address

Refunds

UniversePay supports partial refunds, but only one refund per payment (no multiple partial refunds against the same payment) on the H2H Merchant account.

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Shop ID
• Public Key
• Secret Key
• Provider URL -> (optional)
• Test Mode -> (enable if you are using sandbox credentials)

First request to Corefy API (MIN)

What it does: creates a payment-invoice and redirects the customer to a UniversePay-hosted page to complete a card payment.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

This connector also supports RUB.

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "address": {
          "country": "FR"
        }
      }
    }
  }
}

customer is entirely optional - everything is only used to prefill the hosted form, it never blocks the sale.

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

No Options are configured for this flow.

Constants (fallback fields)

Configured per service. Where available: LANGUAGE, FIRST_NAME, LAST_NAME, EMAIL, PHONE, COUNTRY -> matching customer fields.

Refunds

This flow supports full refunds only (no partial refunds), and only one refund per payment.

Connect Provider account in Corefy Dashboard

Uses the same Provider account connection as Payments above - one connection covers both directions, nothing extra to fill in for payouts specifically.

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends funds to a card.

Payout - MIN (card)

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "0dde9e79-2c64-4703-adaf-93d710633401",
      "service": "payment_card_eur",
      "currency": "EUR",
      "amount": 10,
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

Payout - MAX (card)

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "3c6d2f8e-8a2a-4e7a-9b1a-2f6a7b9c0d1e",
      "service": "payment_card_eur",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567"
      },
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

customer is entirely optional - everything is only forwarded to UniversePay as recipient details. If omitted, your own merchant profile's company name/address is sent as the sender identity instead.

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)

Configured per service. Where available: DESCRIPTION, CUSTOMER_NAME, CUSTOMER_IP, CUSTOMER_EMAIL.