---
title: "Submit customer card details"
method: POST
path: "/v1/checkout/checkout-card-detail"
tags: ["Charge"]
---

# Submit customer card details

`POST /v1/checkout/checkout-card-detail`

Use this endpoint to submit the customers card details

## Request body

- SubmitCardDetails
  - `cardDetails` string — Stringified card details
  - `key` string — encryption key is data encrption is in use, else empty string
  - `orderReference` string — the order reference returned when the order was created
  - `saveCard` boolean — if true, this this user cardn will be saved for the user's future use. Note the process is not complete until the user-card verification endpoints are called to authenticate the user's phone number.
  - `deviceInformation` DeviceInformation — Contains browser information for the device making the api calls
    - `httpBrowserLanguage` string — Browser language
    - `httpBrowserJavaEnabled` boolean — true if Java is enabled in the browser in use
    - `httpBrowserJavaScriptEnabled` boolean — true if Javascript is enabled in the browser in use
    - `httpBrowserColorDepth` string — Browser color depth
    - `httpBrowserScreenHeight` string — Browser scren height
    - `httpBrowserScreenWidth` string — Browser screen weidth
    - `httpBrowserTimeDifference` string — Browser time difference
    - `userAgentBrowserValue` string — Browser user agent
    - `deviceChannel` string — Device channel

## Response `200`

OK - your request was successful.

- object
  - `code` string, required — Response Code
  - `description` string, required — Response description
  - `data` SubmitCardDetailsResponse, required
    - `status` boolean — true if the card details were submitted successfully
    - `message` string — Response message describing the transaction status or further instruction for the user like the case of OTP
    - `responseCode` string — response code from the payment gate way. 00 means transaction was successful and completed, T0 means an OTP has been sent to the user and should be entered next, SO means 3D Secure authentication is required and the client application needs to redirect to the 3D secure page based on the information provided in the secureAuthenticationData field
    - `transactionId` string — the unique id of the transaction just created by the submittion of the card details. This value should be passed back to all API calls that require it.
    - `secureAuthenticationData` SecureAuthenticationData — Authentication data returned from the payment gateway when the payment card requires 3D Secure authentication. This data will be passed to the
      - `jwt` string — jwt token
      - `md` string — encryption key is data encrption is in use, else empty string
      - `acsUrl` string — the order reference returned when the order was created
      - `termUrl` string — the order reference returned when the order was created

## 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)