🚀 Try our APIs instantly — no account needed. See how →
curl --request DELETE \
--url https://api.nomba.com/v1/checkout/tokenized-card-data \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--header 'accountId: <accountid>' \
--data '
{
"tokenKey": "5844858382"
}
'{
"code": "00",
"description": "Success",
"data": {
"status": "true",
"message": "success"
}
}Delete a tokenized card details
curl --request DELETE \
--url https://api.nomba.com/v1/checkout/tokenized-card-data \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--header 'accountId: <accountid>' \
--data '
{
"tokenKey": "5844858382"
}
'{
"code": "00",
"description": "Success",
"data": {
"status": "true",
"message": "success"
}
}Documentation Index
Fetch the complete documentation index at: https://developer.nomba.com/llms.txt
Use this file to discover all available pages before exploring further.
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. In each of the methods, You will get an ACCESS_TOKEN. You need to use an "Authorization" HTTP header to provide your ACCESS_TOKEN. For example: Authorization: {ACCESS_TOKEN}.
The parent accountId of the business.
"890022ce-bae0-45c1-9b9d-ee7872e6ca27"
The request payload required to update the tokenized card data
token key
"5844858382"