Skip to content

Logo

ISX

One ecosystem, endless possibilities

Supports in this guide: Payments, Payouts

Provider website: isx.financial


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

  1. Choose your account type
  2. Get your credentials (from ISX)
  3. Connect in Dashboard
  4. Send an API request

Choose account type

ISX can be connected in different ways (depending on your needs):

  • H2H Merchant account -> card Payments.
  • Provider account -> bank transfer Payouts.

Prerequisites: get from ISX

Contact your ISX account manager to get your account verified and receive the following credentials.

For H2H Merchant account (Payments):

  • Merchant ID -> Corefy field merchant_id.
  • Client Name -> Corefy field client_name -> identifies Corefy to ISX on every request.
  • Workflow -> Corefy field workflow -> an account-specific processing workflow identifier, given by ISX.
  • Bearer Token -> Corefy field bearer_token -> used to authenticate every request.
  • Notification Token -> Corefy field notification_token -> used to verify callback notifications from ISX.
  • Save Instant Token (optional) -> Corefy field save_instant_token -> enable to allow recurring charges (see Recurring below).

For Provider account (Payouts):

  • Merchant ID -> Corefy field merchant_id.
  • API Key -> Corefy field api_key.
  • Callback Secret -> Corefy field callback_secret -> used to verify payout callback notifications from ISX.
  • API URL (optional) -> Corefy field api_url.

USD, JPY (Payments). Payout currencies depend on your ISX account setup - check with your Corefy account manager.


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

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Merchant ID
  • Client Name
  • Workflow
  • Bearer Token
  • Notification Token
  • Save Instant Token (optional)
  • Test Mode -> (enable if you are using sandbox credentials)

Choose Currency / Features; check with your Corefy account manager which are enabled for your account.

Success

You have connected ISX H2H Merchant 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.

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,
      "customer": {
        "reference_id": "cus_123"
      }
    }
  }
}

Important

customer.reference_id is required - ISX's own request builder reads the customer object directly (for the client/address block below), so a request with no customer at all is rejected before it ever reaches ISX.

This connector also supports JPY.

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",
        "address": {
          "country": "US",
          "city": "New York",
          "street": "1 Main street",
          "post_code": "10001"
        }
      }
    }
  }
}

customer is optional and is forwarded directly to ISX with no fallback Constants - if omitted, ISX receives empty billing/contact details for that sale.


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

No Constants are configured for this connector.


Options

  • send_money_in_tokenize_request -> optional, boolean - changes how recurring charges on a saved token are validated (see Recurring below).

Recurring (save and charge a token)

If Save Instant Token is enabled on your connection, the first sale registers the card for recurring use with ISX. To charge the saved token later, use Corefy's standard recurring request.

Important

By default (send_money_in_tokenize_request disabled), Corefy does not send an amount/currency to ISX on the recurring charge - instead it checks locally that the amount you're requesting now exactly matches the amount from the original sale that created the token, and rejects the request with an invalid-amount error if it doesn't. Enable send_money_in_tokenize_request if you need to charge a different amount than the original sale - this sends your requested amount/currency to ISX directly instead of enforcing the match.


Refunds

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


Payouts processing (connect Provider account, create payout-invoice)

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Merchant ID
  • API Key
  • Callback Secret
  • API URL (optional)
  • Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected ISX Provider account!


First request to Corefy API (MIN)

What it does: creates a payout-invoice for a bank transfer payout.

Payout - MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "a1c9f6a0-2d5e-4a7b-9b1e-6a3f0d8c7b2a",
      "service": "bank_transfer_eur",
      "currency": "EUR",
      "amount": 100,
      "customer": {
        "reference_id": "cus_123"
      },
      "fields": {
        "beneficiary_first_name": "John",
        "beneficiary_last_name": "Smith",
        "beneficiary_iban": "DE89370400440532013000"
      }
    }
  }
}

Important

For CAD, AUD, USD, NOK, and NZD specifically, Corefy routes the payout through ISX's international remittance rail instead of its standard batch-payout rail - a different request internally, but the same /api/payout-invoices shape from your side. You can send either fields.beneficiary_iban, or fields.beneficiary_sort_code + fields.beneficiary_account_number for a UK-style account - whichever matches the beneficiary's bank.


Extended request (MAX)

Why add extra fields (typical reasons): - Include optional fields required by your specific flow

This connector has no optional request fields beyond MIN - every other supported currency is just a different service value (bank_transfer_<currency>).


Refunds

ISX does not support refunds on the Provider account / Payouts side.


Additional info

  1. Callback routing is automatic (Payments) - Corefy generates the callback/return URLs per transaction, nothing to configure in ISX's own back-office.
  2. Payouts use a signed callback - ISX signs every payout callback with an HMAC-SHA512 signature in the X-Content-Signature header, verified by Corefy against your Callback Secret - a callback that fails this check is rejected.
  3. Active payout reconciliation is also available - in addition to the signed callback, Corefy can actively check a payout's status with ISX.
  4. Account types are independent - the H2H Merchant account (Payments) and Provider account (Payouts) are two separate Dashboard connections with their own credential sets.

FAQ / Troubleshooting

  • Recurring charge rejected with an invalid-amount error -> by default, a recurring charge must match the original sale's amount exactly - enable send_money_in_tokenize_request if you need to charge a different amount
  • Invalid credentials / auth error (Payments) -> verify Merchant ID/Bearer Token for the selected environment
  • Callback signature fails (Payments) -> verify the Notification Token matches what's configured on your ISX account
  • Refund fails on a second attempt -> only one refund per payment is supported
  • Currency or service is not supported -> confirm allowed currencies/features in your ISX account and in Corefy
  • Invalid credentials / auth error (Payouts) -> verify Merchant ID/API Key for the selected environment
  • Payout callback signature fails -> verify the Callback Secret matches what's configured on your ISX account
  • Payout fails for CAD/AUD/USD/NOK/NZD -> these currencies route through ISX's remittance rail; confirm the beneficiary's bank details match what that rail expects (IBAN, or sort code + account number)

Question

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