Partner FAQs

Frequently asked questions from partners across integration, payments, KYC, and more
View as Markdown

Partner Experience

1

Log in to the Partner Dashboard

Go to the Partner Dashboard and login.

2

Select your environment

Note the Environment drop down in the top right. This allows you to select Staging or Production for each page.

4

View your API key

Your API key and API secret are shown for the environment selected in the top right drop down.

5

Switch environments

Change the environment selection to view your API key for Staging and Production.

You can use the Settings page of the Partner dashboard to set the additional partner fee. Enter the desired percentage in FEE PERCENTAGE and click Update.

No. Authentication and sensitive endpoints must be called from backend only to avoid CORS issues and protect API keys.

Submit the additional domain for whitelisting; domain must match exactly with referrerDomain used during session generation.

The “Invalid or Expired Session” error occurs when the same widgetUrl having same sessionId is reused or reopened after it has already been consumed or expired.

Since each sessionId is single-use, once the widget flow is completed, closed, or expires, the same widgetUrl cannot be used again. A new sessionId must be generated for every new user flow.

Widget

Check that you are passing the API key in the parameters. Some parameters can only be used by partners that have had their KYB approved.

You can find out more details about our ❓ Query Parameters.

To submit your KYB use the below link to verify your business and enable your API key for Production. https://forms.transak.com/kyb

You can use our Get Price API for getting price.

These parameters are required to get response from the API.

"fiatCurrency" //eg: EUR
"cryptoCurrency" //eg: HIVE
"paymentMethod" //eg:sepa_bank_transfer
"partnerApiKey" //YOUR_API_KEY
"network" //mainnet
"isBuyOrSell" //BUY
"fiatAmount" / "cryptoAmount" //Any one is required

No, currently we are not supporting that feature.

You can use TRANSAK_WIDGET_CLOSE event name.

You can find more about events here.

No, but you can hide the menu option using the query parameters, then the chat will also be disabled.

No, we are not offering such API as of now.

You can use disableWalletAddressForm in our query parameters to achieve this.

You will need to pass the walletAddress. Then if disableWalletAddressForm is set to true then the wallet address screen will be skipped for the user.

Yeah you can pass meta data using partnerCustomerId & partnerOrderId and please refer Webhooks to know more about web-hooks.

Please refer to our documentation about our integration ​here.

Users On Boarding

No, users are only required to complete KYC once.

When their KYC is approved they only need to log into their Transak account to perform future transactions. They can use the same KYC-approved Transak account with all of our partner integrations.

Yes, we do support this feature. Please refer KYC Reliance for more details.

If two websites are with same company then you can integrate with same API_KEY.

Otherwise you need to submit KYB for each company.

No it is not required in staging. You can use our Sandbox Credentials in staging.

As of now we support only English to communicate.

Gradually we will add other languages as well.

Users must resolve the existing order first (cancel or complete payment). This prevents duplicate or conflicting transactions.

Payments

We create a virtual bank account for each user and currency. So if a Transak user has only made GBP transactions they will be asked to transfer funds each time to a bank account that is unique to them. Any funds that are sent to that unique account are reconciled with transactions made by that user.

If the user transfers funds in multiple currencies they will be assigned a bank account for each currency.

We create a virtual bank account for every user.

Using that, we track the payment.

Transak is dedicated to being transparent about our pricing and fees. There are four variables that are used to calculate the total amount of cryptocurrency received for the chosen amount of fiat:

  1. Partner fee: P
    • A percentage charge applied on the transaction amount on behalf of the partner. This fee is configurable by partners.
  2. Transak fee: T
    • A percentage charge applied on the transaction amount on behalf of Transak. This covers the fiat processing costs so is set depending on the chosen payment method: credit/debit card or bank transfer. Our fees are set out ​​here.
  3. Network/Exchange fee: N
    • This is the sum of the blockchain transaction fees, or gas, that is paid to make the on-chain transfer of the crypto to the user’s wallet address, plus the withdrawal fee the exchange we are using to provide liquidity. These fees vary by blockchain network and cryptocurrency, as well as changing over time depending on network demand. This fee is set by the market not by us.
  4. Exchange rate: R
    • This is the conversion rate from fiat to cryptocurrency. It is calculated by taking an up-to-date quote of the market rate from multiple pricing services and adding a small slippage percentage. The slippage varies by cryptocurrency and is calculated according to the actual rate we are able to get in the market.

To calculate the total amount of cryptocurrency, C, for the specified amount of fiat currency, F, we calculate the total fees, deduct them from the fiat amount then convert the remainder to cryptocurrency at the market rate. The formula for this is as follows:

C =(F - (F x P% + F x T% + N) x R

So in the example screenshot below where the partner fee is 1% and the payment is a SEPA bank transfer, based on the market rates and blockchain transaction fees at the time:

C = (€1000 - (€1000 x 1% + €1000 x 0.99% + €0.59) x 0.0002482224
C = (€1000 - €20.49) x 0.0002482224
C = €979.51 x 0.0002482224
C = 0.24313632

Note that the market rate and network/exchange fee shown in the widget UI is an estimate. The final cryptocurrency amount the user receives is calculated when the fiat payment is settled.

Blockchain

Please refer to our list of Testnets.

Webhook Handling

Ensure your webhook endpoint returns HTTP 200. Also verify that your server logs are not filtering or rejecting the ORDER_COMPLETED event.

Miscellaneous

Please reach out to our customer support at https://support.transak.com/en/

We are allowing 40 requests per IP address in every 10 seconds. If you want to increase the limit then please contact us at support.transak.com.

Use the Get Fiat Currencies API. The minimum and maximum limits are returned in the response and should be used to display limits dynamically.

Headless Apple Pay (No Auth No KYC)

This is only for EU KYC users. Partners must perform an IP-based geography check before loading the flow and restrict non-EEA users. See https://docs.transak.com/features/headless-apple-pay-no-auth-no-kyc#supported-eu-regions

The module does not check whether the user’s device supports Apple Pay. Partners must verify Apple Pay availability on the device before loading the Transak UI SDK.

Transak UI SDK supports React Native only. Web-based integrations are not supported at this time. The package is @transak/ui-components-rn on npm.

No. The Transaction Session, Transaction Process, and Transaction Request Status APIs must be called from the partner backend only. Calls are subject to IP whitelisting so partner needs to share their public egress IPs with Transak to whitelist them.

  • POST /api/whitelabel/lookup/get-quote → returns quoteId
  • POST /api/v2/transaction-session with quoteId + wallet address → returns sessionId
  • Mount <TransakApplePay sessionId={...} /> in your React Native app; the SDK fires onSuccess({ requestId }) after the Apple Pay sheet completes
  • POST /api/v2/transaction-session/request/:requestId/process from the backend → returns the full order, including orderId
  • Poll GET /api/v2/transaction-session/requests/:requestId until the status reaches a terminal state
  • Use GET /api/public/get-order-by-order-id for full order details
  • Refer to the docs for the canonical sequence

Yes, we recommend the Whitelabel Lookup APIs for new integrations. The Whitelabel base URL is https://api-gateway-stg.transak.com (staging) / https://api-gateway.transak.com (production).

Yes. Order webhooks fire for No-Auth / No-KYC Headless Apple Pay orders the same as for any other flow. Webhook events are always keyed by orderId, not by sessionId or requestId. See Order Webhooks.

After the Transaction Process API succeeds. The sessionId and requestId exist earlier in the flow but are not surfaced in webhooks.

Pass partnerOrderId in the Get Quote call (/api/whitelabel/lookup/get-quote). It will be echoed back in the webhook payload. If partnerOrderId is not passed at the quote step, it is treated as null and will be omitted from the webhook payload.

You need a sandbox Apple ID enrolled in Apple’s Sandbox Tester program, configured with a France billing address (the Headless Apple Pay flow is region-restricted). Transak whitelists the Apple account on our side and provides the Apple Pay test cards (from Apple’s official list — note that only a subset of the listed cards reliably go through). Step-by-step setup: Apple Pay Sandbox Testing for Partners.