Skip to main content
POST
Charge a customer using tokenized card data
For a complete guide on response codes and transaction statuses, see Response Codes.
Some banks require the customer to enter an OTP before a tokenized card can be charged. When that happens, the response has otpRequired: true and a transactionId, and the charge stays pending:
  1. Collect the OTP the customer receives from their bank.
  2. Submit it with Submit customer card OTP, sending otp, orderReference and the transactionId from this response.
A charge whose OTP is not submitted within about 15 minutes is marked as failed.

Authorizations

Authorization
string
header
required

Nomba authenticates API calls with OAuth2 HTTP bearer tokens. There are two methods of authentication; Client-Credentials method and PKCE (Proof Key for Code Exchange) method. Both methods return an access token. Send it in the Authorization header: Authorization: Bearer <access_token>.

Headers

accountId
string<uuid>
required

The parent accountId of the business.

Example:

"890022ce-bae0-45c1-9b9d-ee7872e6ca27"

Body

application/json

The request payload required to perform a tokenized payment.

The Tokenized card payment request object

tokenKey
string
required

the token key returned in the webhook

Example:

"7628788443"

order
object

Response

OK - your request was successful.

code
string
required

Response Code

Example:

"00"

description
string
required

Response description. It says the transaction completed even when the charge was declined or needs an OTP, so read data.status and data.otpRequired instead.

Example:

"tokenized transaction completed successfully"

data
object
required