InsideEx

Your Payment Solution Partner

Supports in this guide: Payments

Provider website: insideex.ai

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

Choose account type
Get your credentials (from InsideEx)
Connect in Dashboard
Send an API request

Choose account type

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

If you do payments -> choose Provider account

If you're not sure which one to use, confirm with your Corefy account manager.

Prerequisites: get from InsideEx

Get the following values for your InsideEx project/account:

API Key -> Corefy field api_key -> example: ak_live_7f3a9c21b8 -> where to find: InsideEx backoffice / issued by InsideEx manager. Sent on every request as the x-api-key header, and also used to generate/verify callback signatures.
API URL (optional) -> Corefy field api_url -> currently has a single option, InsideEx's own endpoint (https://api.backendinside.cc) -> leave as default unless your account manager tells you otherwise.

Important

Be sure to check with the manager if you require to provide a white list of IPs, and if so, specify IP addresses from the Corefy list.

Payments processing (connect Provider account, create payment-invoice)

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

API Key
API URL (leave default)

Success

You have connected InsideEx Provider account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice and returns card/bank transfer requisites from InsideEx for the customer to pay with.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
      "service": "card_transfer_uah_invoice",
      "currency": "UAH",
      "amount": 1000,
      "customer": {
        "reference_id": "cus_123"
      }
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "card_transfer_uah_invoice",
      "currency": "UAH",
      "amount": 2500,
      "customer": {
        "reference_id": "cus_123",
        "email": "johnsmith@gmail.com",
        "phone": "380501234567"
      },
      "metadata": {
        "traffic_type": "FTD"
      }
    }
  }
}

customer must include at least one of reference_id, email, or phone - InsideEx rejects the request with INVALID_DETAILS ("customer id is required") if none of the three is present. InsideEx only accepts amounts between 1000 and 29999 UAH - requests outside this range are rejected. The service code is fixed to card_transfer_uah_invoice (card-to-bank-transfer in UAH); InsideEx does not currently support other currencies on this connector.

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

finalize_expired - whether an EXPIRED status from InsideEx is treated as final right away, or left open for a possible later flip to PAID.
traffic_type - classifies the transaction's traffic quality for InsideEx (first-time depositor / standard / VIP).

finalize_expired

What it does: controls how Corefy maps an EXPIRED status from InsideEx. By default, EXPIRED is mapped to Corefy's own Pending status - the transaction stays open, so a later PAID callback from InsideEx can still complete it. When enabled, EXPIRED is mapped straight to Corefy's own Expired status instead - a final, closed state.

When to use: enable it if you want an immediately final outcome for expired transactions and are fine missing InsideEx's occasional late PAID reversal; leave it off (default) if you want Corefy to keep the transaction open and still pick up that late PAID callback.

Default: false (not set) - EXPIRED stays Pending

Allowed values: true / false

traffic_type

What it does: tags the transaction with a traffic-quality classification sent to InsideEx for their own risk/reporting purposes.

When to use: set it if InsideEx or your account manager asked you to classify traffic by customer type. Can also be overridden per request via metadata.traffic_type in the API request, which takes priority over this Dashboard-configured default.

Default: not set

Allowed values: FTD (first-time depositor) / STD (standard/repeat depositor) / VIP

Additional info

Requisites flow, not a redirect. When you create a payment-invoice, Corefy receives card/bank transfer requisites (a card number and the receiving bank's name) directly from InsideEx - there's no hosted payment page to redirect the customer to. Show these requisites to the customer so they can complete the transfer themselves; InsideEx then confirms the final outcome via callback (or by status polling).
Callback authentication and routing. InsideEx signs every callback with a SHA-256 hash over the sorted transaction data plus your API Key; Corefy verifies this automatically - there's no separate callback secret to configure. Callback routing is also automatic: Corefy generates a per-transaction callback URL and sends it to InsideEx as part of each request, so there's nothing to set up in InsideEx's own back-office for this either.

FAQ / Troubleshooting

Invalid credentials / auth error -> verify your API Key is correct and active
INVALID_AMOUNT / amount rejected -> confirm the amount is between 1000 and 29999 UAH
INVALID_DETAILS / "customer id is required" -> the request's customer object needs at least one of reference_id, email, or phone
Not sure which account type to use? -> ask your Corefy account manager

Question

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