Kora

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Public Key
• Secret Key
• Encryption Key
• Test Mode -> (enable if you are using sandbox credentials)

Choose Currency and Features. ZAR, KES, NGN, and GHS are confirmed; 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.

Payment - MIN

POST /api/payment-invoices

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

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "payment_card_ngn_hpp",
      "currency": "NGN",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+23414524688",
        "address": {
          "country": "NG",
          "region": "Lagos",
          "city": "Lekki",
          "full_address": "Osapa, Lekki",
          "post_code": "101010"
        }
      }
    }
  }
}

customer is entirely optional - there are no Constants on this flow, so anything you don't send is simply left out of the request to Kora.

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

Options are configured on the Corefy side and affect how Corefy builds provider requests or processes responses.

Currently available options (1)

• ignore_callback - tells Corefy to disregard Kora's own callback notifications entirely.

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Public Key
• Secret Key
• Test Mode -> (enable if you are using sandbox credentials)

Choose Currency / Features - card, bank transfer, and mobile money are each available in NGN, GHS, KES, and ZAR (12 services total) - see Additional info.

First request to Corefy API (MIN)

What it does: creates a payment-invoice and returns a redirect link to Kora's hosted payment page.

Payment - MIN

POST /api/payment-invoices

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

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "mobile_ngn_hpp",
      "currency": "NGN",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com"
      }
    }
  }
}

customer.name/customer.email are optional and fall back to the Constants below. mobile_ngn_hpp lets the customer pick from Kora's available Nigerian mobile money channels (including OPay and PalmPay) on the hosted page - this connector also supports payment_card_<ccy>_hpp and bank_transfer_<ccy>_hpp (same optional customer), for ccy in ngn/ghs/kes/zar - see Additional info for the full list.

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

Options are configured on the Corefy side and affect how Corefy builds provider requests or processes responses.

Currently available options (1)

• ignore_callback - tells Corefy to disregard Kora's own callback notifications entirely, for this service. Available on every Payment service on this 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. Available on every Payment service on this flow.

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)

• NAME -> customer.name
• EMAIL -> customer.email

Connect Provider account in Corefy Dashboard

Uses the same Provider account connection as Payments above - one connection covers both directions, there's 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 bank account or a mobile money wallet.

Payout - MIN (generic bank transfer)

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "0dde9e79-2c64-4703-adaf-93d710633401",
      "service": "bank_transfer_ngn",
      "currency": "NGN",
      "amount": 10000,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com"
      },
      "fields": {
        "bank_code": "058",
        "account_number": "0123456789"
      }
    }
  }
}

fields.bank_code and fields.account_number are required for the generic bank_transfer_<ccy> service. For a named Nigerian bank service instead (e.g. guaranty_trust_bank_ngn - see Additional info for the full list), fields.bank_code isn't needed - Corefy already knows which bank it is from the service code, so only fields.account_number is required.

Payout - MIN (mobile money)

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "3c6d2f8e-8a2a-4e7a-9b1a-2f6a7b9c0d1e",
      "service": "safaricom_kes",
      "currency": "KES",
      "amount": 1000,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+254712345678"
      }
    }
  }
}

Mobile money payouts need a phone number - send it as customer.phone, or as fields.phone if you'd rather keep it out of customer.

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

Options are configured on the Corefy side and affect how Corefy builds provider requests or processes responses.

Currently available options (1)

• verify_bank_account - validates the beneficiary's bank account with Kora before submitting the payout.

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. Available on the generic bank transfer services, every named Nigerian bank service, and most Kenya/Ghana mobile money services - not on South African bank payouts or Cameroon/Côte d'Ivoire/Egypt mobile money payouts.

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)

• NAME -> customer.name
• EMAIL -> customer.email