Inwizo

Supports in this guide: Payments, Payouts

Provider website: inwizo.com

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

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

Choose account type

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

If you do card payments (H2H, card data sent directly) -> choose H2H Merchant account
If you do redirect payments (customer redirected to a hosted payment page) or payouts -> choose Provider account

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

Prerequisites: get from Inwizo

Inwizo issues the same kind of credentials for each account type below, but the exact field keys differ between them.

For H2H Merchant account:

Account -> Corefy field account -> example: acc_9f2c1a3b -> where to find: Inwizo backoffice / issued by Inwizo manager
Secret Key 1 -> Corefy field secret_key1 -> example: sk1_7d3f8b2a9c1e4560 -> where to find: Inwizo backoffice / issued by Inwizo manager
Secret Key 2 -> Corefy field secret_key2 -> example: sk2_4a6e2d9f1b3c8720 -> where to find: Inwizo backoffice / issued by Inwizo manager
API URL -> Corefy field api_url -> example: https://api.inwizo.com/ -> where to find: Inwizo backoffice / issued by Inwizo manager

For Provider account:

Account -> Corefy field account -> example: acc_9f2c1a3b -> where to find: Inwizo backoffice / issued by Inwizo manager
First Secret Key -> Corefy field first_secret_key -> example: sk1_7d3f8b2a9c1e4560 -> where to find: Inwizo backoffice / issued by Inwizo manager
Second Secret Key -> Corefy field second_secret_key -> example: sk2_4a6e2d9f1b3c8720 -> where to find: Inwizo backoffice / issued by Inwizo manager
API URL -> Corefy field api_url -> example: https://api.inwizo.com/ -> where to find: Inwizo backoffice / issued by Inwizo manager
Test Mode -> Corefy field test_mode -> enable if you are using sandbox credentials

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

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

Account
Secret Key 1
Secret Key 2
API URL

Choose Currency and Features. You can set these parameters according to available currencies and features for your Inwizo account, but it is necessary to check details of the connection with your Corefy account manager.

Success

You have connected Inwizo H2H Merchant account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 100,
      "customer": {
        "reference_id": "55041b5b-adfd-4073-a92b-fd8b495a4cc1"
      },
      "reference_id": "86e68af6-6b95-4cc0-be16-e4df8044604c"
    }
  }
}

customer.email and customer.phone are both optional pass-throughs — Corefy forwards whichever is present, falling back to the connector's Constants (below) if not.

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 100,
      "customer": {
        "reference_id": "bc75bc54-5023-4f98-8c0d-ec5ed7e8f380",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567"
      },
      "reference_id": "08f5e97c-1170-4bda-9625-3bde3c6dcd20"
    }
  }
}

Inwizo also supports RUB (use payment_card_rub_hpp as the service code for RUB).

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

send_merchant_url_in_the_description - replaces the payment description with the merchant account's profile website
use_internal_id_on_reconcile - uses Corefy's own transaction ID instead of Inwizo's ID when checking payment status
send_additional_browser_data - sends extended browser/device fingerprint data with the request

send_merchant_url_in_the_description

What it does: when enabled, replaces the payment description field with the merchant account's own profile website URL, instead of the payment's ID.

When to use: if Inwizo requires or prefers a website URL in the description field for approval/compliance reasons.

Default: "false"

Allowed values: true, false

use_internal_id_on_reconcile

What it does: when checking a transaction's status with Inwizo, sends Corefy's own internal transaction ID instead of Inwizo's own transaction ID.

When to use: enable only if instructed by Inwizo or your Corefy account manager — the default (Inwizo's own ID) is correct for most cases.

Default: "false"

Allowed values: true, false

send_additional_browser_data

What it does: includes an extended browser/device data block (accept header, IP, color depth, screen size, timezone, user agent, etc.) with the Sale request, in addition to the basic user agent/language already sent.

When to use: enable it if Inwizo requires richer device fingerprinting data for fraud/risk checks.

Default: "false"

Allowed values: true, false

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)

EMAIL -> customer.email
PHONE -> customer.phone

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

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

Account
First Secret Key
Second Secret Key
API URL
Test Mode -> (enable if you are using sandbox credentials)

Choose Currency and Features. You can set these parameters according to available currencies and features for your Inwizo account, but it is necessary to check details of the connection with your Corefy account manager.

Success

You have connected Inwizo Provider account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice. This is a redirect (HPP) flow — the customer is sent to Inwizo's hosted page to complete the payment, so no card data is sent in this request.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "card_transfer_kzt_hpp",
      "currency": "KZT",
      "amount": 100,
      "customer": {
        "reference_id": "55041b5b-adfd-4073-a92b-fd8b495a4cc1",
        "name": "John Smith"
      },
      "reference_id": "86e68af6-6b95-4cc0-be16-e4df8044604c"
    }
  }
}

customer.name (or the FIRST_NAME constant) is required for this flow — Inwizo rejects the request without it.

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "card_transfer_kzt_hpp",
      "currency": "KZT",
      "amount": 100,
      "customer": {
        "reference_id": "bc75bc54-5023-4f98-8c0d-ec5ed7e8f380",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567"
      },
      "reference_id": "08f5e97c-1170-4bda-9625-3bde3c6dcd20"
    }
  }
}

Inwizo also supports several other payment methods and currencies via different service codes: card_transfer_azn_hpp, card_transfer_uzs_hpp, card_transfer_eur_hpp, card_transfer_azn_invoice, payment_card_azn_hpp, payment_card_try_hpp, bank_transfer_try_hpp, m10_azn_hpp, emanat_azn_hpp, openbanking_eur_hpp — confirm with your Corefy account manager which are enabled for your account.

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

send_merchant_url_in_the_description - replaces the payment description with the merchant account's profile website
payments_flow - selects the payment flow used with Inwizo (e-com or p2p)
on_notify_email - tells Inwizo whether to send its own email notification to the customer
on_notify_phone - tells Inwizo whether to send its own SMS notification to the customer
language - sets the language used on Inwizo's hosted payment page
finalize_after_hours - sets a custom expiration window (in hours) for the payment

send_merchant_url_in_the_description

What it does: when enabled, replaces the payment description field with the customer's metadata.merchant_url if provided, otherwise the merchant account's own profile website URL, otherwise the payment's ID.

When to use: if Inwizo requires or prefers a website URL in the description field for approval/compliance reasons.

Default: "false"

Allowed values: true, false

payments_flow

What it does: selects which payment flow Inwizo processes the request under.

When to use: set according to your agreement with Inwizo — confirm with your Inwizo/Corefy account manager which value applies to your account.

Default: none set

Allowed values: e-com, p2p

on_notify_email

What it does: tells Inwizo whether to send its own notification email to the customer, when customer.email is provided.

When to use: enable if you want Inwizo to handle customer email notifications for this payment.

Default: "false"

Allowed values: true, false

on_notify_phone

What it does: tells Inwizo whether to send its own SMS notification to the customer, when customer.phone is provided.

When to use: enable if you want Inwizo to handle customer SMS notifications for this payment.

Default: "false"

Allowed values: true, false

language

What it does: sets the language of Inwizo's hosted payment page.

When to use: set to match your customer's expected language.

Default: none set

Allowed values: En, Ru, Az, Kz, Tr, Uz

finalize_after_hours

What it does: sets a custom expiration window, in hours, for the payment to be completed.

When to use: if the default expiration window doesn't fit your flow.

Default: none set (provider default applies)

Allowed values: any positive integer (hours)

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.name
LAST_NAME -> customer.name
EMAIL -> customer.email
PHONE -> customer.phone

Note

These constants are only available for the card_transfer_kzt_hpp service. Other service codes listed above don't have configurable constants.

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

Connect Provider account in Corefy Dashboard

Use the same Provider account connection as for Payments above — one connection covers both Payments and Payouts for Inwizo. If you haven't connected it yet, follow the steps in the Payments (Provider account) section above.

First request to Corefy API

What it does: creates a payout-invoice.

Payout - Actual

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "service": "payment_card_kzt",
      "currency": "KZT",
      "amount": 100,
      "customer": {
        "reference_id": "55041b5b-adfd-4073-a92b-fd8b495a4cc1"
      },
      "fields": {
        "card_number": "4111111111111111"
      },
      "reference_id": "86e68af6-6b95-4cc0-be16-e4df8044604c"
    }
  }
}

fields.card_number is required for card payouts. Inwizo also supports payment_card payouts in EUR, UZS, USD, AZN, and UAH (use payment_card_eur/payment_card_uzs/payment_card_usd/payment_card_azn/payment_card_uah as the service code), plus m10_azn/emanat_azn (using fields.account_number instead of fields.card_number).

Note

No Corefy-side Options or Constants apply to Inwizo payouts.

Additional info

Callback routing is handled automatically (Corefy generates the callback URL per transaction) — signature validation is applied for both Payments and Payouts.

FAQ / Troubleshooting

Invalid credentials / auth error -> verify credentials for the selected environment and account type
Currency or service is not supported -> confirm allowed currencies/features in your Inwizo account and in Corefy
Missing customer data fields -> set constants (see "Constants") or provide fields in the API request
Not sure which account type to use? -> ask your Corefy account manager
Payment rejected for missing customer name -> customer.name (or the FIRST_NAME constant) is required for Provider account payments

Question

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