A Payment Route is a permanent blockchain address your end-customer can pay in or deposit to
When a customer sends crypto β such as BTC, ETH, SOL, USDT, or more β to their payment route address (the "Crypto address" in the above image), Swapped will send these funds to your Swapped Commerce account.
Payment routes are the easiest way to embed stablecoin and crypto deposits into your existing platform.
Payment routes are good for integrators β like you β who want to:
enable customers to login to your platform and deposit crypto
provide end-users with deposit wallet addresses
End-customers who pay in or deposit to a payment route have their funds automatically swept into the Swapped Commerce account owners balance. This means that you can accept deposits from thousands of customers and have a single master balance for your back-office.
Swapped Commerce merchants can further configure auto-conversion and/or auto-withdrawal rules for specific assets. For example, this means you can:
Receive 30+ crypto assets and auto-convert them to USDT or EUR (or any crypto/fiat)
Automatically withdraw deposited cryptos to a 3rd party wallet (e.g to your preferred Ethereum Wallet)
Or, you can combine the two: convert assets to USDT and automatically withdraw it
Want to make sure one asset, like SOL, isn't converted or withdrawn? No problem
You may view the available blockchains and supported cryptocurrencies for a specific blockchain using the below method:
After crypto is sent or deposited to a payment route, the Swapped Commerce integrator will receive webhooks if configured using your dashboard. See more here.
To get started, create your first Payment Route:
Create a new payment route for a merchant
post
Authorizations
X-API-KeystringRequired
Body
externalIdstring Β· max: 100Optional
customerEmailstringOptional
customerNamestring Β· max: 100Optional
Responses
200
Successful
*/*
post
/v1/payment-routes
200
Successful
Now whenever a deposit is made to this blockchain address, you'll receive the funds to the merchant balance, receive an email notification, and receive webhook information to proceed further.
Generally we see merchants store and save the payment route to their customer, so when they come back to deposit or pay again, the same blockchain address can be used each time.
Complying with the Travel Rule
Swapped follows the EU Travel Rule and utilizes SumSub for KYC collection. More info on SumSub's EU Travel Rule implementation can be found here.
When creating a Payment Route, Swapped will include a KYC Link for you the merchant to present to your end-customer. Since Payment Routes are not aware of deposit or pay-in amounts, it is up to you the merchant to determine when to prompt the customer with this KYC Link.
The process is straightforward:
Create a Payment Route, and in the response will be a KYC Link (e.g data.paymentRoutes[0].userKycLink)
Store this in your database, on the user record.
Whenever you want, e.g on first deposit over >1000 EUR, prompt the user to complete KYC to proceed. Display the KYC Link as an iFrame, new tab, or pop-up for the user to complete.
Once completed, we will send a Webhook to you, and additionally if you GET the Payment Route in the future, the KYC Status will be updated (e.g data.paymentRoutes[0].userKycStatus).
Additionally, the user may have used Swapped Ramp previously, in which case they may have already completed KYC previously. You can check if the user has completed KYC with another API Request: Get or Set KYC.
Getting Payment Route Info
Once a Payment Route is created, you can use the following routes to get information about them: