Stablecoin provider due diligence is the written review a buyer's compliance team runs before moving money through a stablecoin payments vendor. It checks who holds each licence, who holds the funds, who verifies and screens customers, how holds and reports work, and what the contract says when the relationship ends. The questionnaire below turns each check into a question.
A Head of Payments forwards the shortlist to compliance with one line: "can we use them?" Compliance cannot answer from a sales deck: it needs the licence for each leg, a statement of who holds the money, and a written split of checks between vendor and buyer. The guide to choosing a stablecoin infrastructure provider covers the commercial shortlist. This post is the compliance pass that comes after it.
What should a stablecoin vendor review cover?
Six areas, in this order, because a bad answer early makes the later ones moot. Ask for the document behind every answer: a sentence costs the vendor nothing, while a licence number or a diagram can be checked.
The six areas of the review and the first document to request in each.
Area | What it settles | First document to ask for |
Licences | Who may legally move your money | Licence list with numbers |
Funds | Who holds the money at each step | Flow-of-funds diagram |
Verification and screening | Who checks customers and transactions | Written split of duties |
Holds and reporting | What stops a payment and who reports it | Hold procedure with time limits |
Security | Whether outsiders tested the controls | Audit and penetration test summary |
Contract and exit | What you get back if you leave | Exit and liability clauses |
Licences: who operates each leg of the flow
One company rarely holds every licence on a cross-border flow, and that is fine. The failure is a vendor that says "we are licensed" without naming which entity holds which licence for which leg. In Brazil, Article 20 of Central Bank of Brazil (BCB) Resolution 520 of November 10, 2025 limits the intermediation and custody of virtual assets to PSAV (Prestadora de Serviços de Ativos Virtuais, Brazil's virtual asset service provider authorization) holders and a closed list of authorized institutions. The PSAV licence guide explains the regime.
# | Question | A good answer contains | Evidence and check |
1 | Which entity holds which licence for my corridors? | One line per leg: entity, licence type, number, regulator | Licence list; look each number up in the regulator's register |
2 | Where is a banking partner's authorization used instead of yours? | The leg, the partner's licence type, and the contract that lets you rely on it | Licence type in writing; whose name appears on the payee's statement |
3 | Are you in a transition or a pending application? | Filing date, protocol number, what you may offer meanwhile | Filing receipt; the regulator's public list |
4 | Which countries can my customers onboard from? | A published list with tiers, not "it depends" | The list and its date |
5 | Which business types do you refuse or review harder? | A published list of both | The list, compared with your customer base |
On Lumx, the Brazilian entity (Lumx Sociedade Prestadora de Serviços de Ativos Virtuais Ltda) filed its application on October 27, 2026 and operates in the transition under Article 88 of Resolution 520, which gave companies already operating 270 days from the resolution taking effect to apply. Lumx US OP LLC is a Money Services Business (MSB) registered with FinCEN. MXN payments run through a partner licensed as an IFPE (a Mexican electronic payment funds institution), COP through a partner licensed as a compañía de financiamiento, and EUR and GBP through a banking partner, with UK clients onboarded by reverse solicitation. Lumx is not a bank, and a banking partner issues the BRL account. Country tiers and business lists are in the Lumx docs.
Funds and wallets: who holds the money at each step
Ask for the diagram before the policy. In Brazil, Article 28 of Resolution 520 requires a virtual asset provider to keep its own funds apart from clients' funds, in payment or deposit accounts in the clients' names.
# | Question | A good answer contains | Evidence and check |
6 | Who holds the funds at each step, and for how long? | A named holder at every step, for fiat and for stablecoin | Diagram; trace one payment through it |
7 | Who holds the wallet keys? | A named custodian, or a statement that the customer does | Custodian contract summary; insurance |
8 | Are my balances kept apart from other customers' and from yours? | One wallet or account per customer, no pooled balance | Written statement; a balance statement for your funds alone |
9 | What happens to funds in flight if you fail? | The legal structure first, then the mechanics | Contract clause; see what happens if a provider fails |
On Lumx, wallets are held by BitGo, which carries insurance. Each customer has its own wallet on each supported network, with no omnibus account: balances are not mixed between customers or with Lumx's own. The balance is stablecoin, not a deposit. The Transfer endpoint sends stablecoin from a wallet to any external address (wallets documentation). See the custodial wallets product page.
Verification and screening: what the vendor checks and what you still do
The usual gap is assuming that the provider handles KYC (know your customer, the verification of an individual) and that this covers everything. It covers the identity check on the people and companies the provider onboards, and KYB (know your business, the verification of a company and its owners) does the same for companies. Neither covers the data you send, the customers you refuse before they reach the provider, or your own reporting. The compliance split in a stablecoin API lays out every task.
# | Question | A good answer contains | Evidence and check |
10 | Who runs KYB and KYC? | The vendor, a named tool, the exact documents requested | Document list per customer type; a sandbox onboarding |
11 | How long does verification take? | A time per tier, stated as a target | Published targets; time your own test |
12 | What is screened, and when? | Sanctions screening at onboarding, on each new destination and before each transaction | Written scope; what happens to a payout to an unscreened address |
13 | How is the travel rule (FATF Recommendation 16) handled? | Who collects the data, for which transfers | Procedure summary; whether it covers external wallets |
14 | Where is the line on paying for my customers' customers? | A written rule and an approval path | The rule; an approved example |
On Lumx, KYC runs on Sumsub and on-blockchain monitoring runs on Chainalysis KYT. KYC Standard targets about 60 seconds and KYB targets one business day. For a business, Lumx asks for formation documents, those of the representative and every owner above 25%, a proof of address and the expected transaction profile (identity verification). A payout destination must be approved first, and approval includes sanctions screening. Every inbound and outbound transaction is screened before it moves, and a transfer to a non-customer's external wallet also goes through Chainalysis KYT. Lumx says it is aligned with the travel rule. Paying for a customer's own customers needs written approval from Lumx compliance (nested payments). See KYB documents by country and beneficial ownership.
Holds and reporting: what stops a payment and who tells the regulator
Every provider holds some payments. What separates them is the procedure: the status you see, the deadline for your answer and what happens after it. Reporting is the second half: a regulated buyer still reports its own transactions, so ask what the vendor reports on top.
# | Question | A good answer contains | Evidence and check |
15 | What triggers a hold, and how am I told? | A status, a webhook and a named channel | Event list; force a hold in the sandbox if it allows one |
16 | How long do I have to answer, and what happens after? | A number of hours and an outcome | The written window; who decides on release |
17 | Which suspicious-activity and tax reports do you file, and which are mine? | The instruments by name, split by entity | Procedure summary; see the COAF reporting guide |
18 | What do you do when an issuer freezes an address I paid? | A written procedure with a contact and a time | Incident procedure; see frozen USDT addresses |
On Lumx, an RFI (request for information, a compliance hold that asks for a document before a transaction clears) exists for the customer, for the account and for the transaction. The customer.rfi and account.rfi webhooks announce the first two. For a transaction on hold, compliance contacts you by email or Slack, usually about the payment's purpose and the parties. The window is 24 hours, after which the transaction may be refunded to the sender (RFI documentation). In Brazil, Lumx reports as the virtual asset provider under IN RFB 1888/2019, IN RFB 2291/2025 (DeCripto) and the Annex II-A report to the BCB under Article 82-A of Resolution 521/2025. A platform that is itself a VASP (virtual asset service provider) in Brazil reports its own operations. In Colombia, by Lumx's own statement dated November 9, 2026, reports to the UIAF (Colombia's financial intelligence unit) are the banking partner's.
Security, audits and the exit clause
A dated report from a named outside firm outweighs a row of badges.
# | Question | A good answer contains | Evidence and check |
19 | Which audits do you hold, and can I read them? | Names, dates, scope | The report or summary; its date |
20 | Has an outside team tested the platform? | A named firm and a cadence | Penetration test summary |
21 | What are the limits by verification tier, and how do increases work? | A published table and a named process | The table; documents an increase needs |
22 | What is every fee, and how long does a quote hold? | An itemized quote with a quote lifetime | Sample quote against a real payment |
23 | If we leave, how do funds and data come out? | A clause with a time limit and an order of repayment | Termination and export clauses |
24 | What is the liability cap and the uptime commitment? | The cap in writing, a public service level | Contract; service-level page |
On Lumx, the platform has been audited by Halborn, runs penetration tests and goes through an annual financial audit. It is SOC 2 and ISO 27001 compliant, not yet certified. The service level is public on the service level page. Pricing is a monthly platform fee plus usage-based per-transaction fees, transparent FX on locked quotes, no pre-funding; no published plans. Limits are in the transaction limits documentation, and an increase goes through Enhanced verification. Exports include transaction CSV files, account statements and an audit trail. Rails are listed on the coverage page.
How to score the answers, and which ones end the evaluation
Score each of the 24 answers from 0 to 2: 0 for no answer, 1 for an answer with no document, 2 for an answer with a document and a check you ran yourself. A vendor with no knockout and the strongest documented answers goes to a paid pilot on one corridor. Send the same sheet to every vendor, with one deadline.
Some answers end the evaluation whatever the score:
The vendor cannot name the entity that holds the licence for a leg you need.
Customer funds are pooled with the vendor's own, or no flow-of-funds diagram exists.
Screening happens at onboarding only, with nothing before each transaction.
Holds have no stated window and no stated channel.
The contract is silent on exit, data export or the order in which funds come back.
The vendor will not answer in writing.
The money laundering red flags are a different list: they describe customer behaviour, not vendor answers.
I would send this questionnaire to two finalists, not the whole shortlist, and ask for the answers in writing so they can go to compliance unedited. I would read the licence and flow-of-funds answers first and the security answers last, because a provider that cannot say who holds the money gains nothing from a clean penetration test. When two vendors land within a few points of each other, I would decide on the hold question: how long a transaction can sit, who says so, and what happens at the deadline.
When a questionnaire is the wrong tool
Skip it when you have not mapped your own money flow: without a corridor, a currency pair and a monthly volume, every answer sounds acceptable and none can be tested. Skip it when one pilot payment would tell you more than the answers, or when the vendor is a regulated bank that already answers a standard third-party risk template. In those cases, send the shorter list from the provider selection guide linked above and run the pilot. Nor does it replace screening your own customers' wallets.
How Lumx answers the questionnaire
Lumx is stablecoin payments infrastructure for businesses that move money between Latin America and the rest of the world: one API to collect, hold, convert, and pay out in BRL, MXN, COP, USD, EUR, and GBP or in USDC and USDT, over local rails such as PIX, SPEI, PSE, Bre-B, ACH, FEDWIRE, SEPA, and Faster Payments, with SWIFT and on-behalf-of payments and collections (POBO and COBO) in USD, EUR, and GBP, plus named virtual accounts, custodial wallets, and KYB/KYC built in.
Send these 24 questions to Lumx as written.
Methodology and sources
We read BCB Resolution 520 of November 10, 2025 in full on November 21, 2026, as a copy of the BCB page hosted by Migalhas, and took Articles 20, 28 and 88. FATF's site answered with an access error, so FATF Recommendation 16 is named without a link or a date. We read the Lumx docs on November 21, 2026, including prohibited activities and settlement times and cut-offs. Statements about Lumx's entities and audits are Lumx's own as of November 21, 2026.
Verified on November 21, 2026. Operational context, not legal, tax, or investment advice.
What is stablecoin provider due diligence?
It is the written review a buyer runs on a stablecoin payments vendor before sending money through it. It covers licences and custody, then checks and holds, then exit terms, and ends with documents and a score. On Lumx, the entity that operates each leg, the custodian and the hold procedure are described publicly, so the review can start from the docs.
Which documents should a stablecoin vendor give a compliance team?
A licence list with numbers, a flow-of-funds diagram, a written split of duties, an audit or penetration test summary, a sample itemized quote and the contract's exit clauses. Lumx publishes its onboarding documents, country tiers and hold procedure in its docs.
Who runs verification, sanctions screening and the travel rule, the vendor or the buyer?
The vendor verifies and screens the customers it onboards. The buyer owns the data it sends, its customer decisions and its reporting, and the travel rule needs a named owner in writing. On Lumx, KYB and KYC run on Sumsub, each payout destination is screened for sanctions before approval, and every transaction is screened before it moves.
What happens when a stablecoin provider puts a transaction on hold?
The payment stops until the provider's compliance team has what it needs, and the buyer has a limited window to answer. On Lumx, compliance contacts the customer by email or Slack with the questions, and the transaction may be refunded to the sender if there is no response within 24 hours.
Does a SOC 2 report replace a due diligence questionnaire?
No. A SOC 2 report tests security controls over a period. It says nothing about who holds the licence for a corridor, where the funds sit or what happens at a hold. On Lumx, the platform has been audited by Halborn, runs penetration tests and goes through an annual financial audit.





