D8 Corporation

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Merchant ID
• Terminal ID
• CA Certificate
• CA Certificate Key (optional)
• API type (optional)
• Verification user / password / API URL (optional)
• Cybersource key / shared secret (optional)
• Tokenization organization ID / MLE key ID / MLE private key (optional)
• Use Cybersource tokenization (optional)
• Test Mode -> (enable if you are using sandbox credentials)

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. Card, Apple Pay, and Google Pay are all supported on this same connection. D8 may return a 3D Secure challenge redirect depending on the card.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "9c005348-0bd2-4e7f-aa64-b50d0660c01d",
      "service": "payment_card_uah_hpp",
      "currency": "UAH",
      "amount": 100
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "06fa1ea9-8a5b-4dbc-b67b-6236b3b9af3d",
      "service": "payment_card_uah_hpp",
      "currency": "UAH",
      "amount": 100,
      "description": "Order #12345",
      "customer": {
        "reference_id": "33cc9165-6ab2-4cee-8d9a-10f05cddbb5a",
        "name": "John Doe",
        "individual_tax_id": "1234567890"
      }
    }
  }
}

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

• card_vs_itn_verification_bins -> optional, array - list of 6- or 8-digit card BINs for which the cardholder is verified against the customer's tax ID/passport before the payment.
• wait_final_status -> optional, boolean - waits for the final payment status in the same request for non-3DS payments.

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 -> D8 parameter)

• LANGUAGE -> language (2-letter language code; used when the customer's browser language is not available)
• LEGAL_ENTITY_ID -> recipientId (used when the legal entity identifier is not set in your merchant profile)

Used only when API type is c2a:

• ACCOUNT_NUMBER -> dstAccNum (recipient account number)
• ACCOUNT_TYPE -> dstAccType (recipient account type, number)
• DST_FIRST_NAME -> dstFname (recipient first name)
• DST_LAST_NAME -> dstLname (recipient last name)
• FOUNDING_SOURCE -> fundingSource (one of CC, CH, DA, CA, MC)
• BUSINESS_APPLICATION_ID -> businessAppId (one of OGG, GPO, TPP, TAA, TAC, TCB, TBD, TGD, TMS, TCA, TCC, TBB, TBI, TFT, TWT)

Refunds

D8 supports partial refunds, but only one refund per payment (no multiple partial refunds against the same payment).

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Merchant ID
• Terminal ID (optional)
• SSL Certificate
• SSL Private Key
• API URL (optional)
• Verification user / password / API URL (optional)
• Test Mode -> (enable if you are using sandbox credentials)

First request to Corefy API (MIN)

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

Payout - MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "3c4d5e6f-7a8b-4c9d-8e02-3f4a5b6c7d8e",
      "service": "payment_card_uah",
      "currency": "UAH",
      "amount": 100,
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

Payout - MAX

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "4d5e6f7a-8b9c-4d0e-8f13-4a5b6c7d8e9f",
      "service": "payment_card_uah",
      "currency": "UAH",
      "amount": 100,
      "customer": {
        "reference_id": "33cc9165-6ab2-4cee-8d9a-10f05cddbb5a",
        "name": "John Doe",
        "individual_tax_id": "1234567890",
        "address": {
          "country": "UA",
          "city": "Kyiv",
          "street": "Main street 1"
        }
      },
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

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

• card_vs_itn_verification_bins -> optional, array - same mechanism as on the H2H Merchant account: for matching card BINs, verifies the recipient (customer.individual_tax_id or passport) against the card via the D8 verification API before paying out.

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.

After the successful connection, fill in constants for the necessary routes in the editing menu.

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 -> D8 parameter)

• FUNDING_SOURCE -> fundingSource (one of CC, CH, DA, CA, MC; default CC)
• BUSINESS_APP_ID -> businessAppId (3-letter code; default GPO)
• LANGUAGE -> language (2-letter language code; default en)
• DETAIL -> detail (payment description; falls back to the request description, then to the operation ID)
• CLIENT_IP -> clientIp (client IPv4/IPv6; falls back to the request user IP)
• SENDER_ACCOUNT_NUMBER -> srcAccNum (sender account number)
• SENDER_ACCOUNT_TYPE -> srcAccType (sender account type, 0-8)
• SENDER_FIRST_NAME -> chFirstName (sender first name)
• SENDER_LAST_NAME -> chLastName (sender last name)
• SENDER_EMAIL -> chMail (sender email)
• SENDER_PHONE -> chPhoneNum (sender phone number)
• SENDER_PHONE_CC -> chPhonceCc (sender phone country code)
• SENDER_ID_TYPE -> senderIdType (sender ID type: CP - company, PS - passport, TX - tax; sent only when D8 requires it)
• SENDER_ID -> senderId (sender identification number; sent only when D8 requires it)
• BILLING_COUNTRY -> baddrCountry (cardholder billing country, numeric ISO 3166-1; falls back from customer.address)
• BILLING_CITY -> baddrCity (cardholder billing city; falls back from customer.address)
• BILLING_ZIP -> baddrZip (cardholder billing ZIP code; falls back from customer.address)
• BILLING_ADDRESS_LINE1 -> baddrline1 (cardholder billing address; falls back from customer.address)

D8 does not support refunds for payouts.