Create Charge

curl -X POST https://api.khaime.com/api/v1/payments/charge \
  -H "X-API-Key: pk_sandbox_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "preview": true,
    "amount": 1440000,
    "currency": "NGN",
    "total_amount": 9000,
    "total_currency": "USD",
    "description": "Design consultation",
    "customer": {
      "email": "jane@example.com",
      "first_name": "Jane",
      "last_name": "Doe",
      "country": "NG"
    }
  }'

curl -X POST https://api.khaime.com/api/v1/payments/charge \
  -H "X-API-Key: pk_sandbox_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 5000,
    "currency": "USD",
    "total_amount": 5000,
    "total_currency": "USD",
    "description": "Order #123",
    "reference": "wc_123_abc",
    "callback_url": "https://store.example.com/order-received/123",
    "customer": {
      "email": "jane@example.com",
      "first_name": "Jane",
      "last_name": "Doe",
      "country": "US"
    },
    "metadata": {
      "wc_order_id": "123",
      "source": "woocommerce"
    }
  }'

# First: GET /pricing/calculate?amount=9000&target_currency=NGN → returns 1440000
curl -X POST https://api.khaime.com/api/v1/payments/charge \
  -H "X-API-Key: pk_sandbox_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 1440000,
    "currency": "NGN",
    "total_amount": 9000,
    "total_currency": "USD",
    "converted_total_amount": 1440000,
    "converted_total_currency": "NGN",
    "description": "Design consultation + shipping",
    "reference": "consult_0042",
    "customer": {
      "email": "client@example.com",
      "first_name": "Emeka",
      "last_name": "Eze",
      "country": "NG"
    },
    "metadata": {
      "service_type": "design_consultation"
    }
  }'

curl -X POST https://api.khaime.com/api/v1/payments/charge \
  -H "X-API-Key: pk_sandbox_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 140000,
    "currency": "NGN",
    "total_amount": 140000,
    "total_currency": "NGN",
    "description": "Handmade leather bag - Ade Leatherworks",
    "reference": "order_8821",
    "sub_merchant_id": 42,
    "customer": {
      "email": "buyer@example.com",
      "first_name": "Tunde",
      "last_name": "Bello",
      "country": "NG"
    },
    "metadata": {
      "order_id": "8821",
      "vendor": "ade-leatherworks"
    }
  }'

# First: GET /pricing/calculate?amount=9000&target_currency=NGN → returns 1440000
curl -X POST https://api.khaime.com/api/v1/payments/charge \
  -H "X-API-Key: pk_sandbox_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 1440000,
    "currency": "NGN",
    "total_amount": 9000,
    "total_currency": "USD",
    "converted_total_amount": 1440000,
    "converted_total_currency": "NGN",
    "description": "Design consultation - Jane Designs",
    "reference": "consult_0043",
    "sub_merchant_id": 77,
    "customer": {
      "email": "client@example.com",
      "first_name": "Emeka",
      "last_name": "Eze",
      "country": "NG"
    },
    "metadata": {
      "service_type": "design_consultation"
    }
  }'

POST

payments

charge

curl -X POST https://api.khaime.com/api/v1/payments/charge \
  -H "X-API-Key: pk_sandbox_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "preview": true,
    "amount": 1440000,
    "currency": "NGN",
    "total_amount": 9000,
    "total_currency": "USD",
    "description": "Design consultation",
    "customer": {
      "email": "jane@example.com",
      "first_name": "Jane",
      "last_name": "Doe",
      "country": "NG"
    }
  }'

curl -X POST https://api.khaime.com/api/v1/payments/charge \
  -H "X-API-Key: pk_sandbox_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 5000,
    "currency": "USD",
    "total_amount": 5000,
    "total_currency": "USD",
    "description": "Order #123",
    "reference": "wc_123_abc",
    "callback_url": "https://store.example.com/order-received/123",
    "customer": {
      "email": "jane@example.com",
      "first_name": "Jane",
      "last_name": "Doe",
      "country": "US"
    },
    "metadata": {
      "wc_order_id": "123",
      "source": "woocommerce"
    }
  }'

# First: GET /pricing/calculate?amount=9000&target_currency=NGN → returns 1440000
curl -X POST https://api.khaime.com/api/v1/payments/charge \
  -H "X-API-Key: pk_sandbox_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 1440000,
    "currency": "NGN",
    "total_amount": 9000,
    "total_currency": "USD",
    "converted_total_amount": 1440000,
    "converted_total_currency": "NGN",
    "description": "Design consultation + shipping",
    "reference": "consult_0042",
    "customer": {
      "email": "client@example.com",
      "first_name": "Emeka",
      "last_name": "Eze",
      "country": "NG"
    },
    "metadata": {
      "service_type": "design_consultation"
    }
  }'

curl -X POST https://api.khaime.com/api/v1/payments/charge \
  -H "X-API-Key: pk_sandbox_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 140000,
    "currency": "NGN",
    "total_amount": 140000,
    "total_currency": "NGN",
    "description": "Handmade leather bag - Ade Leatherworks",
    "reference": "order_8821",
    "sub_merchant_id": 42,
    "customer": {
      "email": "buyer@example.com",
      "first_name": "Tunde",
      "last_name": "Bello",
      "country": "NG"
    },
    "metadata": {
      "order_id": "8821",
      "vendor": "ade-leatherworks"
    }
  }'

# First: GET /pricing/calculate?amount=9000&target_currency=NGN → returns 1440000
curl -X POST https://api.khaime.com/api/v1/payments/charge \
  -H "X-API-Key: pk_sandbox_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 1440000,
    "currency": "NGN",
    "total_amount": 9000,
    "total_currency": "USD",
    "converted_total_amount": 1440000,
    "converted_total_currency": "NGN",
    "description": "Design consultation - Jane Designs",
    "reference": "consult_0043",
    "sub_merchant_id": 77,
    "customer": {
      "email": "client@example.com",
      "first_name": "Emeka",
      "last_name": "Eze",
      "country": "NG"
    },
    "metadata": {
      "service_type": "design_consultation"
    }
  }'

Intro

Create a one-time (or recurring, with a subscription field) payment charge without needing the product in Khaime’s catalog — the endpoint of choice for WooCommerce and custom integrations where products live on the merchant’s own platform.

This is the recommended endpoint for plugin integrations. Use Create Session if your product already lives in Khaime’s catalog.

Context

Create Charge is the entry point for the whole payment flow described in Payments Overview: the currency you send drives Gateway Routing, cross-currency amounts are validated against Calculate Pricing, subscription_frequency_key turns the charge into a subscription, and a successful charge’s transaction_id is what you later pass to Refunds. Payment outcome is confirmed over the payment.succeeded / payment.failed webhooks, not a return value from this call.

Hows

Request body

integer

required

Charge amount in smallest currency unit (cents, kobo) — the customer’s payment currency. Must be calculated using /pricing/calculate when currency conversion is involved — we validate it matches our calculation.

string

required

3-letter ISO currency code for what the customer pays. Example: USD, NGN, GBP

integer

required

The full amount the merchant is collecting, in smallest currency unit of total_currency. This is inclusive of all fees (shipping, handling, etc.) — not just the base product price.Why required: This field is the source of truth for what gets credited to the merchant’s wallet, and anchors our server-side conversion when multicurrency is involved.

No conversion: Pass the same value as amount
Multicurrency: Pass the total in the merchant’s baseline currency (e.g. 8500 for $85.00 USD)
Marketplace: Pass the total in the sub-merchant’s baseline currency

Example: merchant prices a service at

85 USD with

5 shipping = $90 total, customer pays ₦144,000 NGN — set total_amount: 9000, total_currency: "USD".

original_product_amount is accepted as a deprecated alias and will continue to work.

string

required

ISO 4217 currency code for total_amount. This is the merchant’s (or sub-merchant’s) pricing currency.

No conversion: Pass the same value as currency
Multicurrency / Marketplace: Pass the merchant’s baseline currency

original_product_currency is accepted as a deprecated alias and will continue to work.

integer

Your pre-computed conversion of total_amount into currency (the customer’s payment currency). Optional — but strongly recommended when total_currency differs from currency.When provided, we cross-validate:

converted_total_currency must equal currency
converted_total_amount must equal amount (within 1% tolerance)

This lets us catch discrepancies before hitting the exchange-rate API and gives you an explicit paper trail of what rate you applied.Must be provided together with converted_total_currency.

string

The currency of converted_total_amount. Must match currency. Required when converted_total_amount is provided.

string

Human-readable description of the charge. Shown on payment receipts.

string

Your unique reference for this charge. Used for idempotency and reconciliation.

string

Canonical redirect URL after payment.

Paystack: customer returns here after hosted checkout
StartButton: sent through as redirectUrl during payment initialization
Embedded: use return_url in confirmPayment() on the client

string

Camel-case alias for callback_url. Useful for StartButton-oriented integrations.

string

Snake-case alias for callback_url.

string

Set to make this a recurring charge instead of a one-time payment — see Subscriptions for valid keys and behavior.

object

required

Show Customer fields

string

required

Customer’s email address.

string

Customer’s first name.

string

Customer’s last name.

string

Customer country code or country name. Recommended for reporting, fee detection, and customer geography analytics. Examples: GH, NG, United States.

string

Alias for customer.country. Use this if your checkout already stores ISO-2 country codes as country_code.

string

Alias for customer.country. Accepted as a top-level field for storefronts that already send user_country.

string

Alias for customer.country. Accepted as a top-level field and inside metadata.

string

Alias for customer.country. Accepted as a top-level field.

string

Billing country fallback when customer.country is absent. Accepted as a top-level field and inside metadata.

string

Shipping country fallback when customer.country is absent. Accepted as a top-level field and inside metadata.

Send any country value you already have. Khaime normalizes common country names and ISO-2 codes, then stores the resolved value on the transaction for customer geography reports. If no country is provided, embedded/redirect card country may be used after payment; otherwise the transaction may appear as Unknown in geography analytics.

object

Custom key-value pairs attached to the charge. Send strings, numbers, or booleans only — nested objects/arrays are not rejected by validation (there is no scalar-type check server-side), but they can fail silently downstream if the resolved gateway’s API rejects non-string metadata values. Treat this as a hard rule, not just a recommendation.

Show Example

{
  "wc_order_id": "123",
  "source": "woocommerce",
  "line_items": "[{\"name\":\"Widget\",\"qty\":2}]"
}

string

Force a specific gateway instead of Khaime’s automatic currency-based routing (see Gateway Routing). Only stripe or paystack are accepted — you cannot force startbutton or flutterwave through this field, regardless of currency.

boolean

default:"false"

When true, returns a fee and conversion breakdown without creating any database records or calling any payment gateway. Use this to show the customer exactly what they’ll pay before initiating the real charge.All validation still runs — amount mismatch, currency conversion, sub-merchant, etc. — so a successful preview response means your actual charge will go through.See Preview Mode below for the response shape.

Marketplace fields

This field is only relevant if your account is set up as a marketplace operator. See Setup Marketplace to enable marketplace mode.

integer

The Khaime business ID of the sub-merchant this charge is being collected for. Must have active status in your marketplace.When present, the webhook additionally credits the sub-merchant’s wallet for total_amount minus your marketplace commission, in total_currency. Your marketplace wallet is still credited as normal.

How the split works On webhook receipt after a successful payment:

Your marketplace wallet is credited for amount minus the Khaime platform fee — same as a standard charge.
The sub-merchant wallet is additionally credited for total_amount minus your commission, in total_currency. No additional platform fee is deducted from the sub-merchant — it was already taken on the full charge.

Commission is resolved in this order:

Per-merchant commission_rate set via Update Commission
Your portfolio default marketplace_commission_rate
0 if neither is set

The sub-merchant wallet transaction stores the full breakdown in conversion_details:

{
  "source": "marketplace_split",
  "marketplace_id": 15,
  "charge_currency": "NGN",
  "gross_product_amount": 140000,
  "commission_rate": 0.05,
  "commission_amount": 7000,
  "net_credited": 133000,
  "cart_identifier": "intent_abc123"
}

The sub-merchant must have status: active in your marketplace. Pending or suspended sub-merchants will be skipped — your marketplace wallet will still be credited normally.

Response

The response varies based on which gateway Khaime routes to:

Embedded
Paystack
StartButton / Flutterwave

{
  "success": true,
  "data": {
    "charge_id": "charge_a1b2c3d4",
    "payment_gateway": "stripe",
    "client_secret": "pi_3Abc_secret_Xyz",
    "publishable_key": "pk_test_...",
    "merchant_account_id": "acct_1ABC...",
    "transaction_id": "456",
    "fee_details": {
      "base_amount": 5000,
      "transaction_fee": 320,
      "total_amount": 5320,
      "customer_pays_fees": true
    }
  }
}

Use client_secret and publishable_key to mount the embedded payment element. When merchant_account_id is present (direct/marketplace charges), pass it as connectedAccount when initializing Khaime Payment SDK.

Want Apple Pay / Google Pay in the Payment Element? Register your checkout domain first — see Register Payment Method Domain.

{
  "success": true,
  "data": {
    "charge_id": "charge_e5f6g7h8",
    "payment_gateway": "paystack",
    "payment_url": "https://checkout.paystack.com/abc123",
    "access_code": "0peioxfhpn",
    "paystack_reference": "intent_a1b2c3d4",
    "transaction_id": "789",
    "fee_details": {
      "base_amount": 750000,
      "transaction_fee": 48000,
      "total_amount": 798000,
      "customer_pays_fees": true
    }
  }
}

Redirect the customer to payment_url. They return to your callback_url after payment.

{
  "success": true,
  "data": {
    "charge_id": "intent_0abc2d3c-558e-4db8-80bf-b2c267203f64",
    "payment_gateway": "startbutton",
    "payment_url": "https://pay-sandbox.startbutton.tech/#/shc-arw6qxtuxa",
    "startbutton_reference": "sb_1776282522145_2lgw9sczh",
    "amount": 25563,
    "currency": "GHS",
    "status": "pending",
    "mode": "live",
    "payment_type": "one_time",
    "description": "Order #2496 from testing-khaime-woocommerce",
    "partner_reference": "wc_2496_xHzrUp9r",
    "transaction_id": 6815,
    "transaction_v2_id": 32875,
    "fee_details": {
      "base_amount": 25563,
      "transaction_fee": 1534,
      "total_amount": 25563,
      "customer_pays_fees": false,
      "is_international": true
    }
  }
}

Redirect the customer to payment_url. If you supplied callback_url, redirectUrl, or redirect_url, Khaime forwards the resolved redirect to the gateway and stores it in metadata for downstream processing. Which of StartButton or Flutterwave handles a given African currency is a platform configuration detail — the response shape is the same either way (payment_gateway reflects whichever was used).

Gateway routing

The currency field determines which gateway processes the payment — see Gateway Routing for the full mapping:

Currency	Gateway
NGN	Paystack
GHS, KES, ZAR, TZS, UGX, XAF, XOF	Flutterwave or StartButton
USD, EUR, GBP, CAD, AUD, and most other supported currencies	Stripe

Preview mode

Pass "preview": true in the request body to calculate fees and FX conversion without creating a charge. The response is identical in structure to a normal charge response except:

preview: true is set at the top level
No charge_id, client_secret, payment_url, or transaction_id — no gateway was called
No database records are created

{
  "success": true,
  "message": "Charge preview calculated successfully",
  "data": {
    "preview": true,
    "payment_gateway": "paystack",
    "mode": "sandbox",
    "is_international": true,
    "business_country": "US",
    "customer_country": "NG",
    "customer": {
      "currency": "NGN",
      "base_amount": 1440000,
      "transaction_fee": 92160,
      "total_charged": 1440000,
      "pays_fees": false
    },
    "business": {
      "currency": "USD",
      "priced_amount": 9000
    },
    "conversion": {
      "original_amount": 9000,
      "original_currency": "USD",
      "converted_amount": 1440000,
      "converted_currency": "NGN",
      "exchange_rate": 1600
    }
  }
}

customer and business are always in different currencies when multicurrency is involved — do not compare customer.base_amount with business.priced_amount directly. Use the conversion.exchange_rate to relate them. conversion is only present when currency differs from total_currency.

Typical workflow:

1. POST /payments/charge  { preview: true, ...fields }
   → Show breakdown to customer
2. Customer confirms
3. POST /payments/charge  { ...same fields, no preview }
   → Actual charge created, payment URL / client secret returned

Amount validation (double check)

Both you and Khaime calculate the charge amount independently — they must match. Your workflow:

Call /pricing/calculate with total_amount and target_currency
Use the returned local.amount as your amount in the charge request
Optionally, pass converted_total_amount and converted_total_currency to make your pre-computed conversion explicit
We recalculate using the same conversion service and verify they match

Why double validation? This ensures both parties agree on the conversion. If there’s a mismatch, something is wrong — either a bug, stale rate, or manipulation attempt.

There are two different tolerance checks, easy to conflate: if you supply converted_total_amount, it’s compared against amount with a 1% tolerance. Separately, whenever the server recalculates the expected charge amount itself (the normal path when converted_total_amount is omitted), it uses a wider 2% tolerance to absorb exchange-rate cache drift between your request and Khaime’s own rate refresh.

# Step 1: Get the converted amount
curl "https://api.khaime.com/api/v1/pricing/calculate?amount=9000&target_currency=NGN" \
  -H "X-API-Key: pk_sandbox_your_key"
# Returns: { "local": { "amount": 1440000, "currency": "NGN" } }

# Step 2: Use that amount in your charge
curl -X POST "https://api.khaime.com/api/v1/payments/charge" \
  -H "X-API-Key: pk_sandbox_your_key" \
  -d '{
    "amount": 1440000,
    "currency": "NGN",
    "total_amount": 9000,
    "total_currency": "USD",
    "converted_total_amount": 1440000,
    "converted_total_currency": "NGN",
    ...
  }'

Error codes

Status	Error code	Message	Fix
`400`	`PAYMENT_AMOUNT_MISMATCH`	`Amount mismatch`	Your `amount` doesn’t match our calculation. Use `/pricing/calculate` to get the correct amount.
`400`	`PAYMENT_AMOUNT_MISMATCH`	`converted_total_amount does not match amount`	Your pre-computed conversion differs from `amount`. Ensure both represent the charge total in the same currency.
`400`	`PAYMENT_AMOUNT_MISMATCH`	`converted_total_currency must match the charge currency`	`converted_total_currency` must equal `currency`.
`400`	`VALIDATION_MISSING_FIELD`	`Both converted_total_amount and converted_total_currency must be provided together`	Supply both fields or neither.
`400`	`VALIDATION_MISSING_FIELD`	Missing `amount`, `currency`, or `customer.email`	Include `amount`, `currency`, `customer.email`.
`400`	`VALIDATION_MISSING_FIELD`	Missing `total_amount` / `total_currency`	Include `total_amount` and `total_currency` (or their aliases `original_product_amount` / `original_product_currency`).
`400`	`PAYMENT_CURRENCY_UNSUPPORTED`	`Unable to convert from X to Y`	Currency conversion failed — try again or use a supported currency.
`404`	`BUSINESS_NOT_FOUND`	`Merchant not found`	The authenticated merchant record couldn’t be resolved.
`401`	—	Invalid API key	Check your `X-API-Key` header.
—	(no validation error)	Nested metadata values are not rejected at request time — there is no server-side scalar check. A gateway may reject them downstream instead. Keep metadata values scalar as a precaution, not because you’ll get a clean error if you don’t.

curl -X POST https://api.khaime.com/api/v1/payments/charge \
  -H "X-API-Key: pk_sandbox_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "preview": true,
    "amount": 1440000,
    "currency": "NGN",
    "total_amount": 9000,
    "total_currency": "USD",
    "description": "Design consultation",
    "customer": {
      "email": "jane@example.com",
      "first_name": "Jane",
      "last_name": "Doe",
      "country": "NG"
    }
  }'

curl -X POST https://api.khaime.com/api/v1/payments/charge \
  -H "X-API-Key: pk_sandbox_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 5000,
    "currency": "USD",
    "total_amount": 5000,
    "total_currency": "USD",
    "description": "Order #123",
    "reference": "wc_123_abc",
    "callback_url": "https://store.example.com/order-received/123",
    "customer": {
      "email": "jane@example.com",
      "first_name": "Jane",
      "last_name": "Doe",
      "country": "US"
    },
    "metadata": {
      "wc_order_id": "123",
      "source": "woocommerce"
    }
  }'

# First: GET /pricing/calculate?amount=9000&target_currency=NGN → returns 1440000
curl -X POST https://api.khaime.com/api/v1/payments/charge \
  -H "X-API-Key: pk_sandbox_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 1440000,
    "currency": "NGN",
    "total_amount": 9000,
    "total_currency": "USD",
    "converted_total_amount": 1440000,
    "converted_total_currency": "NGN",
    "description": "Design consultation + shipping",
    "reference": "consult_0042",
    "customer": {
      "email": "client@example.com",
      "first_name": "Emeka",
      "last_name": "Eze",
      "country": "NG"
    },
    "metadata": {
      "service_type": "design_consultation"
    }
  }'

curl -X POST https://api.khaime.com/api/v1/payments/charge \
  -H "X-API-Key: pk_sandbox_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 140000,
    "currency": "NGN",
    "total_amount": 140000,
    "total_currency": "NGN",
    "description": "Handmade leather bag - Ade Leatherworks",
    "reference": "order_8821",
    "sub_merchant_id": 42,
    "customer": {
      "email": "buyer@example.com",
      "first_name": "Tunde",
      "last_name": "Bello",
      "country": "NG"
    },
    "metadata": {
      "order_id": "8821",
      "vendor": "ade-leatherworks"
    }
  }'

# First: GET /pricing/calculate?amount=9000&target_currency=NGN → returns 1440000
curl -X POST https://api.khaime.com/api/v1/payments/charge \
  -H "X-API-Key: pk_sandbox_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": 1440000,
    "currency": "NGN",
    "total_amount": 9000,
    "total_currency": "USD",
    "converted_total_amount": 1440000,
    "converted_total_currency": "NGN",
    "description": "Design consultation - Jane Designs",
    "reference": "consult_0043",
    "sub_merchant_id": 77,
    "customer": {
      "email": "client@example.com",
      "first_name": "Emeka",
      "last_name": "Eze",
      "country": "NG"
    },
    "metadata": {
      "service_type": "design_consultation"
    }
  }'

Whys

total_amount / total_currency are required (not just amount / currency) because they’re the source of truth for what the merchant is owed — amount alone tells Khaime what the customer paid, but not what that should convert back to for wallet crediting. Requiring both, plus the double-validation described above, lets Khaime catch a wrong conversion before money moves rather than after. Marketplace commission resolves through a fallback chain (per-merchant rate → portfolio default → zero) so operators can set sane platform-wide defaults without having to configure every sub-merchant individually.

Why nots

This endpoint does not require a Khaime catalog product — if you want catalog-backed checkout instead, use Create Payment Intent.
payment_gateway cannot force startbutton or flutterwave — only stripe and paystack are valid overrides.
Metadata values are not schema-validated for type — sending nested objects/arrays won’t be rejected here, but can fail silently at the gateway. Keep values scalar.
A charge to a pending or suspended sub-merchant is not rejected outright — it’s silently skipped for the sub-merchant credit while your marketplace wallet is still credited normally, so check sub_merchant_id status ahead of time if the split is load-bearing for your flow.

API Reference

Account

Products & Pricing

Payments

Integration Guides

Commerce API

Subscriptions

Marketplace

Intro

Context

Hows

Request body

Marketplace fields

Response

Gateway routing

Preview mode

Amount validation (double check)

Error codes

Whys

Why nots

​Intro

​Context

​Hows

​Request body

​Marketplace fields

​Response

​Gateway routing

​Preview mode

​Amount validation (double check)

​Error codes

​Whys

​Why nots

Intro

Context

Hows

Request body

Marketplace fields

Response

Gateway routing

Preview mode

Amount validation (double check)

Error codes

Whys

Why nots