Headless Cards
Headless Cards is a lightweight, embeddable UI module that allows partners to offer credit/debit card payments directly within their own application without loading any widget.
Problem Statement
Currently, Transak requires loading the full widget for card payments, which forces users to go through multiple screens before reaching the payment form. This creates friction and limits partner control over the payment experience.
Here are some of the key challenges with the current approach:
Our Solution
Headless Cards exposes just the card payment form as a standalone, embeddable component. Partners control where it sits, how it looks, and what happens after payment. Transak handles all the payment infrastructure in the background.
Here are some of the key benefits of the Headless Cards solution:
How does it work?

Current Limitations
How to integrate?
User Authentication
You can use either of the following authentication options:
Please refer to the tutorial on how to create partner access token.
User KYC
KYC is a mandatory step in compliance with regulatory requirements. Each user should be KYC Approved. You can use either of the following KYC options:
Generate a quote using the Quote API
Call the Get Quote API to get a quote for the transaction. Pass the apiKey, fiat amount, fiat currency, crypto currency, network, and order type.
Set paymentMethod to credit_debit_card while creating a quote.
A successful response returns a quoteId.
Create a transaction session (using Backend only)
Call the Transaction Session API from your backend using the quoteId, successUrl, failureUrl and the user’s wallet address. You can optionally pass a config and billingAddress object to customise the look and feel of the card component and billing details.
A successful response returns a sessionId.
Load the Card Component via Transak UI SDK
Use the Transak UI SDK to render the card payment component. Pass the sessionId received in the previous step.
JS
React
React Native
Error codes
The onError callback receives a code value. Use it to handle specific failure scenarios:
Process the payment with requestId (using Backend only)
Once the SDK fires onSuccess with a requestId, call the Transaction Process API from your backend to complete the payment and create the order.
A successful response returns the full order details with redirectUrl.
Open the redirectUrl in a browser or WebView
Open the redirectUrl returned in the previous step in the browser or webview to complete any 3DS or bank authentication required by the payment provider.
Upon completing the transaction, the user will be redirected to either the successUrl or failureUrl you passed in the Transaction Session API.
Track the requestId (using Backend only)
Call the Transaction Request Status API to check whether the request has been processed. Poll this endpoint until the status reaches a terminal state.
Once you receive an orderId, use the Get Order by ID API to fetch full order details.
API Overview
Creates a transaction session using a quote ID and wallet address, returns a sessionId to initialise the card payment component.
Processes the card payment using the requestId returned by the SDK’s onSuccess callback, completing the order creation.
Polls the status of the requestId until it reaches a terminal state.