D8Corporation

Website: www.d8corporation.com

Set up Merchant Account

Step 1: Create Merchant Account

To create an account send connection request to D8 contact manager. Submit the required documents to verify your account and gain access.

Step 2: Get required credentials

Credentials that have to be issued:

• d8__merchant_id → Merchant ID
• d8__terminal_id → Terminal ID
• d8__ssl_cert → SSL Certificate
• d8__ssl_private_key → SSL Private Key
• d8__api_url → API URL (optional, default ecomx.mtb.ua:8443/payments/v1/ for production and ecomm-test.mtb.ua/payments/v1/ for test environment)

"Having issues with your credentials?" Please contact our support team!

Connect Provider Account

Step 1. Connect provider account at the Corefy Dashboard

Press Connect at D8 Provider Overview page in 'New connection' section and press Connect button to open Connection form.

Enter credentials:

• Merchant ID
• Terminal ID
• SSL Certificate
• SSL Private Key
• API URL (optional, default ecomx.mtb.ua:8443/payments/v1/ for production and ecomm-test.mtb.ua/payments/v1/ for test environment)

You have connected D8 provider account!

API examples:

Min/max data set to create a payout invoice for payment_card_uah service

PAYOUT

POST /api/payout-invoices HTTP/1.1
{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "service": "payment_card_uah",
      "currency": "UAH",
      "amount": 100,
      "test_mode": true,
      "fields": {
        "card_number": "5122********0027"
      }
    }
  }
}

Constants for payouts

If some parameters are not sent in the transaction creation request, they will take the values from the set constants.

Here is a list of constants with their corresponding parameters:

• FUNDING SOURCE → fundingSource (Money Transfer funding source, AN..2; default CC)
• BUSINESS APP ID → businessAppId (Money Transfer Business Application Identifier, AN..3; default GPO)
• LANGUAGE → language (ISO 639-1 two-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 in the postAdditionalData step when the provider requires it)
• SENDER ID → senderId (sender identification number; sent in the postAdditionalData step when the provider requires it)
• BILLING COUNTRY → baddrCountry (cardholder billing country, numeric ISO 3166-1, e.g. 804; falls back from the customer address)
• BILLING CITY → baddrCity (cardholder billing city; falls back from the customer address)
• BILLING ZIP → baddrZip (cardholder billing ZIP code; falls back from the customer address)
• BILLING ADDRESS LINE 1 → baddrline1 (cardholder billing address; falls back from the customer address)

H2H Merchant account (Payments)

Prerequisites: get from D8

Get the following values for your D8 H2H account:

• Merchant ID -> Corefy field merchant_id -> where to find: issued by your D8 manager
• Terminal ID -> Corefy field terminal_id -> where to find: issued by your D8 manager
• CA Certificate -> Corefy field ca_cert -> format: upload a certificate file -> where to find: issued by your D8 manager
• CA Certificate Key (optional) -> Corefy field ca_cert_key -> format: upload a private key file -> where to find: issued by your D8 manager
• API type (optional) -> Corefy field api_type -> card_payment (default) or c2a (card-to-account) -> confirm with your D8 manager which one applies to your terminal

Optional, only if you use cardholder verification (see the card_vs_itn_verification_bins option below):

• Verification user -> Corefy field verification_user
• Verification password -> Corefy field verification_password
• Verification API URL -> Corefy field verification_api_url

Optional, only if you use Cybersource network tokenization:

• Cybersource key -> Corefy field cb_key
• Cybersource shared secret -> Corefy field cb_shared_secret
• Tokenization organization ID -> Corefy field tokenize_org_id
• Tokenization MLE key ID -> Corefy field tokenize_mle_key_id
• Tokenization MLE private key -> Corefy field tokenize_mle_private_key -> format: upload a private key file

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

{
  "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"
      }
    }
  }
}

Additional info

1. D8 does not send callbacks to Corefy for H2H payments: payment statuses are updated by status requests (reconciliation).
2. Refunds are supported for the full amount only (no partial or multiple refunds).

3. D8 supports Apple Pay and Google Pay with decryption on the Corefy side.

   For more information, visit:

   • How to Integrate Apple Pay with Corefy: Full Technical Walkthrough
   • How to Integrate Google Pay with Corefy: Full Technical Walkthrough

FAQ / Troubleshooting

• Invalid credentials / auth error -> verify the certificate, key and IDs for the selected environment (test_mode)
• Currency or service is not supported -> confirm allowed currencies/features in your D8 account and in Corefy
• Payment declined with invalid cardholder -> the card BIN is listed in card_vs_itn_verification_bins; send customer.individual_tax_id (or passport data) of the card owner
• Not sure which account type to use? -> ask your Corefy account manager