Unity Finance

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• API User
• API Key
• Checkout ID
• Secret Key
• Payment Method
• Test Mode -> (enable if you are using sandbox credentials)

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. Unity Finance may return a 3D Secure challenge redirect depending on the card.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "2f4a6c80-1b3d-4e5f-8a0c-7b9d1e3f5a7c",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

This connector also supports CAD, INR, USD, PLN, ZAR, AUD, HUF, RON.

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "3a5b7c91-2c4e-4f60-9b1d-8c0e2f4a6c8e",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "individual_tax_id": "12345678900",
        "address": {
          "country": "FR",
          "region": "IDF",
          "city": "Paris",
          "full_address": "1 Main street",
          "post_code": "75000"
        }
      }
    }
  }
}

customer is entirely optional. For first/last name, the priority is customer.name first, then the name embossed on the card. Everything sent to Unity Finance (name, address, etc.) is automatically transliterated to Latin.

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 Constants are configured for this connector.

Options

• provider_url_blacklist -> optional, string, slash-separated list of hostnames - if the redirect URL Unity Finance returns for a sale points to one of these hosts, skips redirecting the customer there and checks the final status immediately instead.
• 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.
• ignore_sale_resolution_message -> optional, boolean - omits Unity Finance's own resolution message text when a 3D Secure challenge is required, instead of including it.

Refunds

This connector does not support refunds on the H2H Merchant account - use the Provider account if you need refunds.

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• API User
• API Key
• Checkout ID
• Secret Key
• Test Secret Key (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 Unity Finance-hosted page to complete the payment. Unity Finance supports a wide range of local methods - card, Apple Pay, Google Pay, bank transfer, UPI (India), PIX (Brazil), BLIK (Poland), Bancontact, MB WAY, Multibanco, Skrill, and Neteller - the exact set available depends on what's enabled for your specific account - check with your account manager.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "4b6c8d02-3d5f-4a71-8c2e-9d1f3a5c7e9f",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "5c7d9e13-4e6a-4b82-8d3f-0e2a4c6e8f0a",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com"
      }
    }
  }
}

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 Constants are configured for this flow.

Options

• replace_result_url -> optional, boolean - sends separate success/failure/pending redirect URLs to Unity Finance instead of one shared result URL.
• send_customer_referer -> optional, boolean - additionally sends your return URL as a customer referrer value.
• psp_gateway -> optional, enum, configured per payment method/currency - when more than one processing route is available for a specific method on your account, lets you pick which one handles it; confirm with your account manager which options apply and which is right for you.

Refunds

Unity Finance supports partial refunds, but only one refund per payment (no multiple partial refunds against the same 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 via card, bank transfer, SEPA transfer, IMPS/Paytm (India), or PIX (Brazil), depending on what's enabled for your account. Required fields vary by method - the Dashboard shows the exact field list once a method is selected.

Payout - MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "6d8e0f24-5f7b-4c93-8e4a-1f3b5d7f9a1b",
      "service": "payment_card_eur",
      "currency": "EUR",
      "amount": 10,
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

Payout - MAX

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "7e9f1a35-6a8c-4da4-8f5b-2a4c6e8f0a2c",
      "service": "payment_card_eur",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith"
      },
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

customer is entirely optional - name, when sent, is forwarded as the receiver's name. This connector also supports USD, KZT for card payouts.

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

• psp_gateway -> optional, enum, configured per payout method/currency - when more than one processing route is available for a specific method on your account, lets you pick which one handles it; confirm with your account manager which options apply and which is right for you.