---
title: "Charge a customer using tokenized card data"
method: POST
path: "/v1/checkout/tokenized-card-payment"
tags: ["Online Checkout"]
---

# Charge a customer using tokenized card data

`POST /v1/checkout/tokenized-card-payment`

You can use this endpoint to charge a customer's card using the tokenized card details.

## Headers

- `accountId` string, uuid, required

## Request body

- TokenizedCardPaymentRequest — The Tokenized card payment request object
  - `order` Order
    - `orderReference` string — reference of the online checkout order to be created
    - `customerId` string — customer id
    - `callbackUrl` string, required — Merchant callback url for redirect after payment
    - `customerEmail` string, required — customer email
    - `amount` number, double, required — Amount to pay
    - `currency` 'NGN' | 'CDF' | 'USD', required — ISO 4217 currency code. Use NGN for Nigerian checkout. For DRC accounts, use CDF or USD — NGN is not supported for DRC and will be rejected.
    - `accountId` string — If specified, this is the account where the funds will be deposited.
    - `allowedPaymentMethods` string[] — Optional list of payment methods to display on the checkout page. If not provided, all supported methods for your account and region will be shown. Supported values: Card, Transfer, Nomba QR, USSD, Buy Now Pay Later (Nigerian checkout); MOMO, Intl Card, Apple Pay (DRC checkout).
    - `splitRequest` object — Contains accounts where the inflow will be split into
      - `splitType` 'PERCENTAGE' | 'AMOUNT' — The type fo split to use, either PERCENTAGE or AMOUNT
      - `splitList` object[]
        - `accountId` string — The account Id whose wallet will be credited when the order is paid
        - `value` number — The percentage or the order amount or the actual value to credit to this account.
    - `orderMetaData` object — Arbitrary key-value metadata to attach to the order. Keys and values must be strings. Stored on the order and returned in webhook payloads. Special key: set "region" to "CD" to route this order through DRC checkout (e.g. for a Nigerian merchant accepting DRC MoMo payments).
  - `tokenKey` string, required — the token key returned in the webhook

## Response `200`

OK - your request was successful.

- object
  - `code` string, required — Response Code
  - `description` string, required — payment successful
  - `data` TokenizedCardPaymentResponse, required
    - `status` boolean — status of the transaction
    - `message` string — some details of the transaction response.

## Other responses

- `400` — The request body sent by merchant did not pass the validation checks
- `401` — The access_token provided to access the resource is missing or invalid.
- `403` — The client does not have the permissions to access this resource
- `404` — The record that the client is trying to access does not exist.
- `429` — The client has maxed out the number of calls within a time period on this resource.
- `500` — Downstream system error.

---

[API](https://skmtc.net/nomba/apis/vendor-api.md) · [All operations](https://skmtc.net/nomba/apis/vendor-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/nomba/vendor-api/revisions/41727ac9be5f/schema)