Skip to content

KYC, KYB and AML for card and stablecoin payment programs: what fintechs must cover

KYC, KYB and AML for card and stablecoin payment programs: what each control does, who owns it, the travel rule, pending US rules, and a launch checklist.

KYC and KYB are the identity checks a payment program runs before anyone can send, receive, or spend money. KYC (know your customer) verifies individuals, KYB (know your business) verifies companies and their owners, and an anti-money laundering (AML) program adds sanctions screening, monitoring, and reporting. Card programs add sponsor bank and network rules. Stablecoin programs add the travel rule.

This guide is for fintech founders and compliance leads launching a card program, a stablecoin program, or both. It explains each control, who owns it in each type of program, and which US rules were still pending in late October 2026. Every rule is linked to the regulation or agency document it comes from.

This guide is general information, not legal or compliance advice. Requirements vary by license, product, and country, so confirm your own obligations with counsel.

Key takeaways

  • KYC is for people, KYB is for companies. KYB includes KYC on each owner of 25 percent or more and on one controlling person.
  • An AML program is more than onboarding. It covers risk assessment, sanctions screening, transaction monitoring, reporting, and records.
  • Card programs run under the sponsor bank's program. Using a program manager or vendor does not remove the bank's responsibility.
  • Stablecoin programs add wallet screening and the travel rule. The OCC's GENIUS Act final rule of October 21, 2026 leaves AML and sanctions rules for issuers to a separate rulemaking.
  • You can buy the controls, but you keep the duty. Write down who owns each one before launch.

What is the difference between KYC and KYB?

KYC confirms that a person is real and is who they claim to be. KYB confirms that a company exists, what it does, and who owns and controls it.

In the US, the bank customer identification program rule at 31 CFR 1020.220 sets the floor for KYC. A written program must collect, at minimum, a name, a date of birth for individuals, an address, and an identification number. It must let the bank "form a reasonable belief that it knows the true identity of each customer."

KYB builds on that. The customer due diligence rule at 31 CFR 1010.230 defines two kinds of beneficial owner for a legal entity customer:

  • The ownership prong: each individual who "owns 25 percent or more of the equity interests" of the company.
  • The control prong: "a single individual with significant responsibility to control, manage, or direct" the company, such as an executive officer.

Each of those people goes through KYC. That is why KYB takes longer than KYC: the company file is quick, and the owners are the work. FinCEN's order FIN-2026-R001 of February 13, 2026 gave covered institutions relief from re-verifying beneficial owners at every new account opening, and it left the 25 percent and control definitions unchanged.

For a longer walkthrough, see what KYB is and KYC vs KYB vs KYT, which adds transaction monitoring to the comparison.

What does an AML program include?

An AML program is the written set of policies and controls a regulated company uses to detect and report money laundering. Identity checks are one part of it. Most of the work happens after the customer is onboarded.

A typical program has six parts:

  1. Risk assessment. A written view of which customers, products, countries, and payment methods carry more risk, and what controls apply to each.
  2. Customer due diligence. KYC and KYB at onboarding, deeper checks for higher-risk customers, and refreshes on a schedule or when behavior changes.
  3. Sanctions screening. Checking customers, owners, counterparties, and wallet addresses against sanctions lists.
  4. Transaction monitoring. Rules and models that flag payments that do not fit the customer's profile.
  5. Reporting. Filing suspicious activity reports with the financial intelligence unit, which is FinCEN in the US.
  6. Records, training, and testing. Keeping records, training staff, naming a compliance officer, and having the program reviewed independently.

For a US money services business, the program rule at 31 CFR 1022.210 requires policies and controls that include "verifying customer identification." Banks, card issuers, and virtual asset firms each have their own version of the rule, and the parts above appear in all of them.

A regulator or bank partner will ask for evidence, so keep the alert, the decision, and the name of the person who made it for every case. AML audit readiness and risk monitoring covers what an examiner samples.

How does sanctions screening work?

Sanctions screening compares the people, companies, and wallets in a payment against government lists of blocked parties. In the US, the Office of Foreign Assets Control (OFAC) publishes those lists.

OFAC's guidance for the virtual currency industry (October 2021) is direct about digital assets. It says sanctions compliance obligations "apply equally to transactions involving virtual currencies and those involving traditional fiat currencies." A stablecoin payment gets no lighter treatment than a wire.

Screening runs at three moments:

  • At onboarding: the customer, and for a business, every owner and controller.
  • On each payment: the sender, the receiver, their banks or wallets, and the countries involved.
  • When a list changes: the whole customer base is rescreened, because a customer who was clear last month may be listed today.

Stablecoin programs screen wallet addresses as well as names, because OFAC has listed digital currency addresses since 2018. How often to rescreen for sanctions covers the schedule.

What is the travel rule for digital asset transfers?

The travel rule requires the institution sending a transfer to pass information about the sender and the receiver to the next institution. It started with bank wires and now covers digital asset transfers between providers.

In the US, 31 CFR 1010.410(f) applies it to a "transmittal of funds in the amount of $3,000 or more." The information that travels includes the sender's name, account number if there is one, and address, plus the amount, the execution date, and the recipient's financial institution.

For virtual assets, the Financial Action Task Force (FATF), the global AML standard setter, applies the same idea through its 2021 guidance on virtual assets. Countries may adopt a de minimis threshold of USD or EUR 1,000. Each country sets its own threshold and data fields, so a program serving several markets follows several versions of the rule.

The data does not ride on the blockchain. Providers exchange it beside the transfer. The travel rule for stablecoin off-ramps shows where it applies on each leg of a payout.

What does a card program add?

A card program adds a sponsor bank and a card network, and both set compliance requirements on top of the law. The bank that issues the card owns the compliance program for every card on its bank identification number (BIN).

Three parties share the work:

  • The sponsor bank is the legal issuer. It answers to its regulator for customer identification, AML, and sanctions across the program.
  • The program manager is the fintech that designs the product and holds the cardholder relationship. It runs onboarding, monitoring, and complaints under the bank's policies.
  • The card network sets program rules, dispute rules, and monitoring thresholds for fraud and chargebacks.

Outsourcing the daily work does not move the responsibility. The 2023 Interagency Guidance on Third-Party Relationships (88 FR 37920) says "the use of third parties does not diminish or remove banking organizations' responsibilities." In practice, the sponsor bank audits the program manager, approves its policies, and can pause the program.

On the identity side, every cardholder in a consumer program goes through KYC before a card is issued. In a corporate program, the company goes through KYB and the employees who get cards are identified to the level the bank's policy requires. Stablecoin card issuing compliance lists each party's duties, and BIN sponsor vs issuer processor vs program manager explains the roles.

Card programs carry two more obligations outside AML. Card data must be protected under the PCI DSS standard, and disputes follow the network's chargeback process. For how a card payment moves from authorization to settlement, start with how card payments work.

What does a stablecoin program add?

A stablecoin program adds wallet screening, the travel rule, and the virtual asset rules of each country where it has customers. It also depends on which stablecoin it uses, because US law now regulates the issuers.

The GENIUS Act, Public Law 119-27, says a permitted payment stablecoin issuer "shall be treated as a financial institution for purposes of the Bank Secrecy Act" (section 4(a)(5)(A)). That puts AML and sanctions duties on the issuer of the token. It does not write the detailed rules.

Those rules are still being made. Here is where each one stood in late October 2026:

RuleWhat it coversStatus
OCC final rule, Bulletin 2026-50, October 21, 2026Reserves, redemption, risk management, custody, applications, and capital for issuers the OCC supervisesFinal, effective January 18, 2027. Bank Secrecy Act, AML, and OFAC requirements "will be addressed in a separate rulemaking in coordination with the Department of the Treasury"
FinCEN and OFAC proposal, 91 FR 18582, April 10, 2026AML and sanctions program requirements for permitted issuers, in a new 31 CFR Part 1033Proposed. Comments closed June 9, 2026. No final rule as of this writing
Customer identification program proposal, published June 22, 2026Identity verification requirements for permitted issuers, proposed by FinCEN and the banking regulatorsProposed. Comments closed August 21, 2026. No final rule as of this writing

Covington's summary of the OCC final rule (October 23, 2026) confirms that both proposals are separate from it and still pending.

Most stablecoin programs are not issuers. A fintech that moves stablecoins for its customers answers to money transmission and money services business rules, sanctions law, and the travel rule, whatever happens to the issuer rules. The GENIUS Act explained for payments teams covers what the Act changes for businesses that use stablecoins without issuing them.

Who owns each control in a card program and in a stablecoin program?

Ownership follows the license. The table shows the usual split. Your contracts decide the details, so get the split in writing.

ControlWhat it doesWho owns it in a card programWho owns it in a stablecoin program
KYCVerifies each individual before they transactThe sponsor bank's program, run day to day by the program managerThe licensed provider that moves the funds, with the platform collecting the data
KYBVerifies each company, its owners, and its controllerThe sponsor bank's program, run by the program manager for corporate cardsThe licensed provider, with the platform collecting ownership documents
Sanctions screeningChecks people, companies, and countries against sanctions listsThe sponsor bank's program, run by the program manager and the processorThe licensed provider, on customers, recipients, and wallet addresses
Transaction monitoringFlags activity that does not fit the customerProgram manager and processor on card activity, overseen by the bankThe licensed provider on transfers and wallets, and the platform on its own product
Travel rulePasses sender and receiver data with a transferApplies to the funds transfers behind the card, handled by the bank and its payment providersThe provider sending or receiving the digital asset transfer
Suspicious activity reportingReports suspected crime to the financial intelligence unitThe sponsor bank files, using cases the program manager escalatesEach licensed provider files for its own obligations
Records and audit trailKeeps the evidence for each decisionEvery party, under the bank's retention policyEvery party, under its own license

A program that issues stablecoin-funded cards sits in both columns at once. The card side follows the bank's program, and the funding and payout side follows the stablecoin provider's. Who owns compliance when you integrate an on-ramp API walks through a full responsibility matrix.

Should you build or buy compliance controls?

Most new programs buy the controls and keep the oversight. Building identity verification, screening, monitoring, and case management from scratch takes months of vendor selection, integration, and policy work. Buying them inside a payment API shortens the launch to the provider's onboarding time plus your own policy.

BlindPay is one example of buying the controls for the money movement around a program. KYC, KYB, sanctions screening, travel rule checks, and compliance review run inside the API flow, before money moves. Its KYC reference lists automated review in about 60 seconds for KYC Standard, and 3 hours to 1 business day for KYC Enhanced and KYB. A payment that needs review shows an on_hold status with a webhook, so your team sees the hold instead of guessing at a delay.

BlindPay does not issue cards and is not a card issuer or acquirer. It runs the funding, collection, and local-currency payout legs around a card or stablecoin program, over rails such as Pix, SPEI, ACH, RTP, SEPA, and SWIFT (POBO/COBO). It received its first US state money transmitter license, from New Jersey, in October 2026, and publishes its status on its licenses page. The card itself still needs a card issuer and that issuer's compliance program.

Buying does not end your part. You still need a written policy, a named compliance owner, and someone who answers requests for information within hours. How to automate KYC and KYB covers the tooling choices.

What should be on a compliance checklist before launch?

  1. Write the AML policy and risk assessment, and name the compliance officer.
  2. List every party in the program and the license each one holds for each country you serve.
  3. Decide which customers get KYC, which get KYB, and what triggers enhanced due diligence.
  4. Collect full owner data for businesses: every owner of 25 percent or more and one controller.
  5. Confirm who screens names and wallet addresses at onboarding, on each payment, and on each list update.
  6. Map which transfers cross a travel rule threshold in each country, and who sends the data.
  7. Agree in writing who files suspicious activity reports and who keeps which records.
  8. Test a held payment and a rejected customer end to end before go-live.
  9. Set a review date for the pending US stablecoin AML rules.

If the program includes cards, add the sponsor bank's own onboarding list. Funding a stablecoin card program covers where compliance sits in the money flows, and virtual cards explained covers the issuing side.

Sources

  • 31 CFR 1020.220, customer identification program requirements for banks, via Cornell Legal Information Institute: law.cornell.edu
  • 31 CFR 1010.230, beneficial ownership requirements for legal entity customers, via Cornell Legal Information Institute: law.cornell.edu
  • 31 CFR 1010.410(f), recordkeeping and travel rule for transmittals of funds, via Cornell Legal Information Institute: law.cornell.edu
  • 31 CFR 1022.210, AML programs for money services businesses, via Cornell Legal Information Institute: law.cornell.edu
  • FinCEN, order FIN-2026-R001, February 13, 2026
  • OFAC, Sanctions Compliance Guidance for the Virtual Currency Industry, October 2021: ofac.treasury.gov
  • FATF, Updated Guidance for a Risk-Based Approach to Virtual Assets and Virtual Asset Service Providers, 2021: fatf-gafi.org
  • Interagency Guidance on Third-Party Relationships: Risk Management, 88 FR 37920, June 9, 2023
  • GENIUS Act, Public Law 119-27, July 18, 2025: govinfo.gov
  • OCC Bulletin 2026-50, October 21, 2026: occ.gov
  • FinCEN and OFAC, proposed rule for permitted payment stablecoin issuers, 91 FR 18582, April 10, 2026
  • Covington, key takeaways on the OCC final rule, October 23, 2026: cov.com
  • BlindPay, KYC requirements: docs

What to do next

Fill in the ownership table for your own program, with a company name in every cell. Any cell you cannot fill is the first thing to fix. Then read stablecoin card issuing compliance if you issue cards, or the travel rule for stablecoin off-ramps if you pay out, and talk to BlindPay about running KYC, KYB, and screening inside your payment flow.

This article is general information, not legal, tax, or financial advice.

FAQ

One API.
Multiple payment rails.

Blind Pay, Inc. (“BlindPay”) is a United States-based financial technology and payments infrastructure company, incorporated in the State of Delaware on May 2, 2024. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000277566153. BlindPay is not a state-licensed money transmitter and does not, in its own capacity, engage in regulated money transmission services. All such regulated activities are conducted exclusively through, and under the licenses of, duly authorized financial institution partners. BlindPay's role is limited to providing financial technology, virtual account management, payment processing, and related payments infrastructure services that facilitate payment flows and account functionalities. These services are provided in coordination with its licensed partners and in compliance with applicable federal MSB requirements and relevant state regulatory frameworks.

Blind Pay, LLC (“BlindPay”) is a Delaware limited liability company formed on June 24, 2025. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000318334247 and is listed in the Nationwide Multistate Licensing System (“NMLS”) under NMLS ID #2745309.

BLIND PAY SOCIEDADE PRESTADORA DE SERVIÇOS DE ATIVOS VIRTUAIS LTDA. (“BlindPay”) is a Virtual Asset Service Provider (“VASP”) operating in Brazil. The company is presently completing the regulatory adaptation process required of Virtual Asset Service Provider Companies (SPSAV) under Central Bank of Brazil Resolution No. 520/2025, and remains subject to the transitional regime set forth in Article 88 of that Resolution. Registered address: Avenida Princesa Isabel, nº 15, Sala 1405, Edifício Martinho de Freitas, Centro, Vitória/ES, 29010-361.

BlindPay is a stablecoin API that enables individuals and businesses to move money worldwide.