Skip to content

Logo

CardifyX

Supports in this guide: Payments

Provider website: cardifyx.com

What you need to do for start processing transactions (brief summary)

  1. Get your credentials (from CardifyX)
  2. Connect in Dashboard
  3. Send an API request

Prerequisites: get from CardifyX

To create an account, send a connection request to CardifyX (contact their manager directly) and submit the required documents to verify your account.

Get the following values for your CardifyX account:

  • API Key -> Corefy field api_key -> where to find: issued by CardifyX for your account
  • Signing Key -> Corefy field signing_key -> used to verify the Signature header on callbacks -> where to find: issued by CardifyX for your account

EUR, USD, GBP only.

Payments processing (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • API Key -> api_key
  • Signing Key -> signing_key
  • Currency / Features -> choose values available for your account

Success

You have connected CardifyX H2H Merchant account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice for a direct card payment (BASIC_CARD). Card data itself is collected and submitted separately through Corefy's secure checkout/SDK layer, not as part of this request. If CardifyX requires 3-D Secure for the card, the payment moves to an auth-required status and the customer is redirected to complete authentication before the result is final.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6f1a2b3c-4d5e-4f60-8a71-9b2c3d4e5f60",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "100045821"
      }
    }
  }
}

Important

CardifyX requires customer.first_name, customer.last_name, customer.email, and customer.phone to accept the payment. If any of these are missing from the request and no matching Constant is configured for your account (see below), CardifyX rejects the payment with a validation error - Corefy does not substitute a placeholder value for a missing field.

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "a1b2c3d4-5e6f-4789-8a0b-1c2d3e4f5061",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "100045821",
        "first_name": "John",
        "last_name": "Muller",
        "email": "muller1996@gmail.com",
        "phone": "+37126212007",
        "date_of_birth": "1996-06-29",
        "address": {
          "country": "DE",
          "city": "Berlin",
          "full_address": "Friedricstasse, 12",
          "post_code": "10110"
        }
      }
    }
  }
}

Important

  • customer.date_of_birth is optional (format YYYY-MM-DD) and is only sent to CardifyX when present.
  • customer.address.full_address, .city, .country, and .post_code are sent to CardifyX as the billing address.

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.

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)

  • FIRST_NAME -> customer.first_name
  • LAST_NAME -> customer.last_name
  • EMAIL -> customer.email
  • PHONE -> customer.phone
  • FULL_ADDRESS -> customer.address.full_address
  • CITY -> customer.address.city
  • COUNTRY -> customer.address.country
  • POST_CODE -> customer.address.post_code
  • DATE_OF_BIRTH -> customer.date_of_birth

Refunds

CardifyX supports partial refunds, but only one refund per payment (no multiple partial refunds against the same payment). The original payment's transaction ID is always required to process a refund and to reconcile a refund's status.

Additional info

  1. Active reconciliation is available - Payments support both the asynchronous callback (HMAC-SHA256 Signature header, verified using your signing_key) and an active status request.
  2. No fake/placeholder customer data is ever sent - if customer.first_name, .last_name, .email, .phone, address fields, or .date_of_birth are missing from your request and no matching Constant is configured, Corefy simply omits that field from the request to CardifyX rather than substituting a made-up value.
  3. No recurring - this connector does not support saving/charging a token through Corefy.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify your api_key
  • Payment rejected with a customer validation error -> CardifyX requires customer.first_name, .last_name, .email, and .phone - provide them in the request or configure the matching Constants
  • Currency or service is not supported -> only EUR, USD, and GBP are available for this connector
  • Refund fails on a second attempt -> only one refund per payment is allowed
  • Callback signature mismatch -> confirm your signing_key matches the one configured on the CardifyX side

Question

Still looking for help connecting your CardifyX account? Please contact our support team!