Skip to main content
The transaction type defines the required and optional request parameters. Always validate the specified type before building the request.
Checkout (order) flows do not require KYC/KYB. If the payment is linked to an order (order_code or executor_id: order_transaction), verification is skipped.For financial transactions (standalone api_transaction payments), fiat-related types (pixcrypto, cardcrypto, cardfiat, cryptopix, fiatcrypto) require approved KYC/KYB when you send payer_email or payer_wallet. Pure crypto never requires KYC/KYB. See StarkPay overview.
1

Create a crypto transaction

Create a crypto transaction to any token on any chain (ANY-TO-ANY)

Response Expected 

How can you sign a transaction?

This example illustrates the mandatory transaction submission flow. Direct submission is not allowed and may result in failure or rejection. All transactions must be submitted exclusively through the API’s broadcast service, which is responsible for validating, propagating, and processing requests.
You may use an external wallet connection provider, such as Privy.io, to interact with the user’s wallet and sign the transaction. However, never send the transaction directly using methods like sendTransaction. The transaction must only be signed and then submitted to the API’s broadcast endpoint.
2

Create an on-ramp transaction

Create an on-ramp transaction for fiat payment

Response Expected

With the required data in hand, simply display the payment QR code so the user can scan it using their banking app and complete the payment.  From that point on, our backend automatically monitors the transaction status and, once confirmed, delivers the crypto assets directly to the registered wallet.
3

Create a credit card transaction

Create a credit card transaction
Card payment support is currently limited to the CardCrypto method.  This method has specific operational rules and limits that must be aligned in advance with the sales team.Only one-time transactions are currently supported. The enablement process has a minimum lead time of 7 days and may vary depending on regulatory requirements and jurisdiction.
Use the tokenization endpoint to process card data, avoiding the direct handling and storage of sensitive card information.  Tokenization provides a higher level of security and helps ensure compliance with regulatory requirements.

Response expected

When using tokenized card data, the payment request payload must follow the structure below:
To use any payment method involving the traditional financial system (off-chain), such as PIX, fiat currency, or card payments, you must contact the sales and account management team to complete KYC and/or KYB procedures –– This process ensures proper operational alignment, customer profiling, and compliance with applicable regulations.