Exactly

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• API Key
• Project ID (optional)
• Callback Secret Key (optional)
• API URL (optional)
• New API -> (enable to use Exactly's newer integration - required for Apple Pay/Google Pay; off by default, which keeps the original integration)
• Save Instant Token -> (enable if you plan to use instant/recurring payments, or to later pay out back to the same card)
• Acquirer BIN, Acquirer Merchant ID, MPI API Key, Acquirer Country Code, Acquirer Country Code Source (optional, see Additional info)

Choose Currency and Features. You can set these parameters according to available currencies and features for your Exactly account (USD, EUR, GBP, RUB, UAH, PEN confirmed); enabling Apple Pay/Google Pay as a feature requires New API to also be enabled.

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_usd_hpp",
      "currency": "USD",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "date_of_birth": "2000-12-31",
        "address": {
          "full_address": "1st Avenue North",
          "country": "US",
          "city": "New York",
          "post_code": "10115"
        }
      }
    }
  }
}

customer is entirely optional at the code level, but note that name/phone/date_of_birth are only forwarded to Exactly when Send Customer Data is enabled below (on by default), and the address block only when Send Source Address is enabled (also on by default). This connector also supports EUR, GBP, RUB, UAH, and PEN (use payment_card_<currency>_hpp as the service code).

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 (9)

• refund_with_delay - reports a refund as RECONCILE_REQUIRED instead of an immediate final result, when Exactly's response supports a delayed check.
• transaction_lifetime - how long (in minutes) the transaction stays valid.
• arn_reconcile_delay_hours - waits before expecting the ARN (Acquirer Reference Number) to be available via reconciliation (New API only).
• set_threeds_data - adds 3DS data (ARN, verification, CAVV) to the response for successful transactions.
• use_external_mpi - uses a third-party MPI service for 3D Secure instead of Exactly's own built-in 3DS.
• set_original_resolution_message - sets the resolution message to Exactly's own raw result code.
• send_customer_data - sends customer name, phone, and date of birth to Exactly.
• send_source_address - sends the customer's address (country, city, street, post code, region) to Exactly.
• generate_customer_birth_date - auto-generates a random date of birth (1955-2003) when none is provided.

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• API Key
• API URL (optional)

First request to Corefy API (MIN)

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

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "0dde9e79-2c64-4703-adaf-93d710633401",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "7976b4ce-fadd-4585-baa0-6b02c65351dc",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "address": {
          "country": "US"
        }
      }
    }
  }
}

customer.email/phone are optional pass-throughs. customer.address.country (or the DEFAULT_LANGUAGE constant below) selects the language on Exactly's hosted page; if neither is set, a platform default is used. This connector also supports EUR, GBP, CHF, PLN, and MXN (use payment_card_<currency>_hpp as the service code).

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)

• DEFAULT_LANGUAGE -> customer.address.country - a country code selecting which language Exactly's hosted payment page is shown in, used when the request doesn't include customer.address.country.

Connect Provider account in Corefy Dashboard

Uses the same Provider account connection as Payments above.

First request to Corefy API (MIN)

What it does: creates a payout-invoice that sends funds back to a card previously saved via an H2H payment with Save Instant Token enabled - this is a token-based payout, not a raw card number payout.

Payout - MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "0dde9e79-2c64-4703-adaf-93d710633401",
      "service": "card_token",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "address": {
          "country": "US",
          "city": "New York",
          "full_address": "1st Avenue North"
        }
      },
      "fields": {
        "token": "tok_1a2b3c4d5e6f"
      }
    }
  }
}

Payout - MAX

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "7976b4ce-fadd-4585-baa0-6b02c65351dc",
      "service": "card_token",
      "currency": "USD",
      "amount": 10,
      "description": "Refund to original card",
      "customer": {
        "reference_id": "cus_123",
        "address": {
          "country": "US",
          "city": "New York",
          "full_address": "1st Avenue North"
        }
      },
      "fields": {
        "token": "tok_1a2b3c4d5e6f"
      }
    }
  }
}

fields.token (the token payload returned from an earlier H2H payment made with Save Instant Token enabled) is required, as is customer.address - a request missing either is rejected before reaching Exactly. currency should match whatever currency the original tokenized payment used. description is optional.

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