Bind a customer reference
Use a stable identifier from your platform to associate a collection address with a customer or business account. Keep that mapping in your own system.
CRYPTO PAYMENT GATEWAY
Accept stablecoin and crypto transfers with collection addresses, incoming-payment monitoring, KYT screening and notifications to your platform. Turn an on-chain payment into a usable event for your business.

Illustrative flow · Your platform controls its ledger.
Link a collection address to your own customer reference. When that customer sends crypto to the address, Satogate monitors the transfer and reports the result against the same reference.
Use a stable identifier from your platform to associate a collection address with a customer or business account. Keep that mapping in your own system.
Track the supported asset, network, destination and confirmation status. A transaction being broadcast and a transfer being confirmed are different events.
Receive the payment result so your backend can credit the customer’s account or update an order, using your own business rules.
A recurring top-up flow keeps the collection address tied to the customer, while each incoming transfer has its own transaction record.
Your platform requests an address linked to its customer reference.
Your customer sends crypto using the displayed asset, network and address.
Satogate tracks the incoming transfer and its confirmation state.
Your backend processes the notification and updates its ledger.
Connect a confirmed deposit to a customer balance in a platform, app or service. Your platform decides when that balance becomes available.
Use customer references and transaction records to connect an on-chain transfer with the corresponding business activity.
Look up transfer and settlement records when investigating a missing credit, a confirmation delay or a reconciliation difference.
KYT transaction screening adds an on-chain risk perspective to your collection workflow. Review a payment’s transaction context alongside its confirmation state before applying your own acceptance and account-crediting rules.
Use transaction-level screening to help identify on-chain risk associated with incoming crypto payments.
A confirmed transfer tells you funds arrived. KYT provides a different signal for your platform’s risk review.
Connect the customer reference, asset, network and transaction hash with your payment and risk-review records.
Crypto Payment Gateway
1%
per transaction
Standard gateway processing fee for crypto collections.
Contact usThis rate applies to the Crypto Payment Gateway. Business fiat conversion and personal crypto purchases are quoted separately.
Looking for business fiat conversion?Our business off-ramp service helps you convert crypto into fiat for delivery to your business bank account. You can also buy crypto with business funds through our on-ramp service. Arrange the conversion separately from your customer collection flow.
Agree the collection assets, networks, confirmation rules and callback handling for your integration. Show the exact asset and network beside every address, and define how your platform handles unmatched transfers or amount differences.
The Crypto Payment Gateway handles incoming crypto transfers. Users who need to buy USDT with fiat can use the separate Satogate buying experience, in partnership with Legend Trading. A completed purchase does not by itself mark a merchant order paid.
Use your platform’s customer reference as the link between its ledger and a collection address. Your backend handles the confirmed payment result.
Choose a persistent customer reference and store its address, asset and network mapping.
Show the collection details in your product and monitor the incoming transfer.
Validate the callback, match the customer and transaction, and apply your KYT review and account-crediting rules. Make repeated delivery safe to process.
Check recorded transfer status before crediting a disputed or missing deposit.
ILLUSTRATIVE EVENT MAPPING · NOT AN API PAYLOAD
Keep a record of processed transfers so repeated notifications cannot credit the same deposit twice.
Use the same payment acceptance foundation for software clients. With x402, a paid resource returns payment requirements, the client supplies payment information, and your integration verifies and settles payment before releasing access. Match payment state to the request and make retries safe to process.