Swapped Commerce implements the Travel Rule and requires merchants to share relevant customers data
KYC for Payment Links
To configure KYC in your Payment Links, navigate to the Merchant Settings, and find the setting for "Customer KYC Requirement". There are multiple settings to select from that you can configure to your business needs.
KYC for Payment Routes
The Payment Routes dashboard and API support KYC Links. It is up to you, the merchant, to determine when to prompt your users to complete KYC. You can find more details about how KYC Links work with Payment Routes here.
Check KYC Status for a user/email via API
Users of Swapped may KYC with one or more of our products. The first step is to check if we have any previously submit KYC submissions for a given user. Check this using their email:
Get user status by email
get
Authorizations
X-API-KeystringRequired
Query parameters
customerEmailstringRequired
Responses
200
Successful
*/*
get
/v1/users
200
Successful
If necessary, request any additional information from the customer.
Supply KYC Data
Swapped follows regulations according to the EU Travel Rule. Swapped works with SumSub for KYC, and you may learn more about the Travel Rule here.
For transactions below 1,000 EUR, Swapped requires the Name for an end-user.
For transactions above 1,000 EUR, Swapped requires the Name, Address, and Tax ID Number for an end-user.
You can build out your own form to request such information from the end-customer. In either case, the merchant can supply the relevant data via API when creating (1) a payout, (2) creating a payment route, or (3) creating a payment link.
Once the KYC data is shared, we will run a synchronous check on the customer, and store it for future validation.