Alliancepay

Connect in Corefy Dashboard (H2H Merchant account)

Step 1 — Open connection form

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

Step 2 — Fill in fields and select settings

• Merchant ID
• Payment Key (upload text file)
• Private Key (upload text file)
• Service Code
• API type → select the API type for your AlliancePay account

Additionally, choose Currency and Features according to what is enabled for your AlliancePay account.

First request to Corefy API (MIN)

What it does: creates a payment-invoice.

Payment — MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "payment_card_uah_hpp",
      "currency": "UAH",
      "amount": 10
    }
  }
}

Payment — MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "payment_card_uah_hpp",
      "currency": "UAH",
      "amount": 10.04,
      "customer": {
        "reference_id": "cus_123",
        "email": "sss@gmail.com"
      }
    }
  }
}

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

Currently available options:

• api_type — selects the API type for your AlliancePay account.

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.

If a field is missing in the API request, Corefy can take the value from the configured Constants.

Use constants when you cannot provide certain customer/merchant fields dynamically in your API requests.

Priority (predictable rule):

1. If a value is present in the request → Corefy uses the request value
2. Else if the constant is set and value isn't present in the request → 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)

• STREET → customer.address.street
• COUNTRY → customer.address.country
• CITY → customer.address.city
• NAME → customer.name

Connect in Corefy Dashboard (Provider account)

Step 1 — Open connection form

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

Step 2 — Fill in fields (provider → Corefy)

• Merchant ID → merchant_id
• Service code → service_code
• Payment key → payment_key (upload a text file)
• Private key → private_key (upload a text file)

First request to Corefy API (MIN)

What it does: creates a payout-invoice.

Payout — MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "service": "payment_card_uah",
      "currency": "UAH",
      "amount": 10,
      "fields": {
        "card_number": "411111******1111"
      }
    }
  }
}

Payout — MAX

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "service": "payment_card_uah",
      "currency": "UAH",
      "amount": 10,
      "customer": {
        "reference_id": "33cc9165-6ab2-4cee-8d9a-10f05cddbb5a",
        "name": "John Doe",
        "address": {
          "country": "UA",
          "city": "Lviv",
          "street": "Main street"
        }
      },
      "fields": {
        "card_number": "411111******1111"
      }
    }
  }
}

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.

If a field is missing in the API request, Corefy can take the value from the configured Constants.

Use constants when you cannot provide certain customer/merchant fields dynamically in your API requests.

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)

• STREET → customer.address.street
• COUNTRY → customer.address.country
• CITY → customer.address.city
• NAME → customer.name