Skip to content

Logo

ISX

One ecosystem, endless possibilities

Supports in this guide: Payments

Provider website: isx.financial

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

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

Prerequisites: get from ISX

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

  • 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).
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
    }
  }
}

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).

Additional info

  1. Callback routing is automatic - Corefy generates the callback/return URLs per transaction, nothing to configure in ISX's own back-office.
  2. No payouts - this connector does not support payouts through Corefy.

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 -> verify Merchant ID/Bearer Token for the selected environment
  • Callback signature fails -> 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

Question

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