Cardaq

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Secret Key
• Terminal ID (optional)
• Google Pay Merchant ID / Google Pay Gateway Merchant ID (optional, if using Google Pay)
• Apple Pay Merchant ID / Display Name / Merchant ID Certificate / Certificate Password (optional, if using Apple Pay)
• Save Instant Token -> enable if you plan to use stored-credential recurring charges after an initial payment
• 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. Cardaq may return a 3D Secure challenge redirect depending on the card.

Payment - MIN

POST /api/payment-invoices

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

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "payment_card_gbp_hpp",
      "currency": "GBP",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "date_of_birth": "1990-01-01",
        "address": {
          "country": "GB",
          "region": "London",
          "city": "London",
          "full_address": "1 Main street",
          "post_code": "SW1A 1AA"
        }
      }
    }
  }
}

customer is entirely optional - email/full_address/post_code fall back to the Constants below if not sent; everything else is simply left blank on Cardaq's side if omitted.

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

Configured per feature (card, Apple Pay, Google Pay):

• send_descriptor -> optional, boolean - sends your configured dynamic descriptor on the statement.
• send_all_types_ip_address -> optional, boolean - by default, Corefy only sends the customer's IP if it's a valid IPv4 address; enable this to send it regardless of format (e.g. IPv6).

Card payments only:

• select3ds -> optional, Automatic (default) or Manual - Automatic lets Cardaq's own hosted flow handle the 3D Secure challenge end-to-end; Manual has Corefy manage the challenge redirect itself. Ask your account manager which one applies to your 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.

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)

Configured for card and Apple Pay payments (not Google Pay).

Currently available constants (constant -> Corefy API field)

• LANGUAGE -> checkout language
• CUSTOMER_EMAIL -> customer.email
• ADDRESS -> customer.address.full_address
• POST_CODE -> customer.address.post_code
• SDWO_MERCHANT_ID -> an optional sub-merchant/operator identifier - only relevant if your account manager tells you it's needed for your setup.

Refunds

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