Skip to content

KYC and KYB in payments: what gets checked, how long it takes and whether to build or buy

KYC verifies people and KYB verifies businesses. See the data collected, timings, sanctions and the travel rule, and when to build or buy.

KYC (Know Your Customer) verifies that an individual is who they say they are. KYB (Know Your Business) verifies a company and the people who own or control it. In payments, both run before a customer can send or receive money, and screening and monitoring continue afterward. Automated checks for standard-risk individuals can take about a minute; business and enhanced checks need a human and take hours.

This guide follows the compliance lifecycle of a payment product, as of November 2026, with BlindPay as the worked example. For definitions, see KYC vs KYB vs KYT and what is KYB. This page takes a different angle: what data you must collect, what each step costs in time, and whether to build or buy.

Key takeaways

  • KYC covers people. KYB covers a business and then runs KYC-style checks on its owners and controllers.
  • Standard checks can be automated. Enhanced due diligence and every business check involve a human reviewer.
  • Sanctions screening and the travel rule work at the payment level, not just at onboarding.
  • BlindPay documents about 60 seconds for KYC Standard and 3 hours to 1 business day for KYC Enhanced and KYB Standard.
  • Build in-house only if compliance is your product. Otherwise buy it inside the payment API and keep your own program obligations.

What is the difference between KYC and KYB?

KYC identifies a person. KYB identifies a company and then identifies the people behind it, because a company can hide who really controls the money.

A KYB file therefore contains both entity data and a set of individual verifications. In the US, the customer due diligence rule at 31 CFR 1010.230 defines a beneficial owner as anyone who owns 25 percent or more of the equity of a legal entity customer, plus a single individual with significant responsibility to control, manage or direct it. Other countries use similar tests with their own thresholds.

What data is collected for individuals and businesses?

Individuals give identity and address data, and businesses add registration data and owners. The table uses BlindPay's KYC requirements as the example.

DataIndividual (KYC Standard)Business (KYB Standard)
NameFirst and last nameLegal name, optional alternate name
IdentityDate of birth, tax ID, government ID document and selfieTax ID and formation date
AddressResidential address, proof of address optional on StandardBusiness address and proof of address (required)
DocumentsID front (back optional)Incorporation document and proof of ownership
ContactEmail, phone optionalEmail, website (required), phone optional
PeopleThe individualAt least 1 owner, beneficial owner or controlling person, each verified with their own ID, selfie and proof of address

Document quality drives speed. BlindPay accepts PDF, JPEG or PNG up to 5 MB, asks for the whole document to be visible and rejects screenshots, photos of screens and cropped or blurry images. Printed or photocopied documents are also a common rejection cause.

What are standard and enhanced due diligence?

Standard due diligence is the baseline check for normal-risk customers. Enhanced due diligence adds proof and explanation for higher-risk customers, usually with a human reviewer.

BlindPay's tiers show how this works in practice:

LevelApplies toReviewTypical time
KYC StandardIndividuals in standard-risk countriesAutomatedAbout 60 seconds
KYC EnhancedIndividuals from high-risk countriesManual3 hours to 1 business day
KYB StandardBusinessesManual3 hours to 1 business day

Enhanced KYC adds a mandatory proof of address, a source of funds document and a stated purpose of transactions. Individuals from high-risk countries must use Enhanced, and Standard is rejected for them. There is no enhanced KYB tier, and a legacy light tier is no longer issued. Timings come from BlindPay's KYC docs as of November 2026.

What are sanctions screening and the travel rule?

Sanctions screening checks customers and counterparties against government lists, and the travel rule makes sender and recipient information travel with a transfer. Both apply to payments, not only to account opening.

Sanctions screening. Providers screen people, businesses and increasingly wallet addresses, and they refuse to serve restricted countries. BlindPay's supported countries page says countries under sanctions or outside its risk appetite are not supported at all, and that tiers are reviewed as sanctions and risk assessments change. See ongoing sanctions screening for rescreening cadence.

The travel rule. In the US, 31 CFR 1010.410(f) requires a transmittor's financial institution or intermediary to include specified information in transmittal orders of $3,000 or more, and 1010.410(e) sets recordkeeping at the same threshold for nonbank institutions. The international standard is FATF Recommendation 16, which FATF revised in 2025, so check FATF's page for current thresholds. For digital-asset flows, see the travel rule for stablecoin payins.

What is ongoing monitoring?

Ongoing monitoring watches customers and transactions after approval for activity that does not fit the profile. Verification at day one does not cover a customer's behavior in month six.

It has three parts: transaction monitoring for unusual patterns, periodic review of customer files, and rescreening against updated lists. At BlindPay, a monitoring system flags suspicious payins and payouts as on-hold transactions, and the compliance team reviews each one. If it cannot clear the flag, it sends a Request for Information (RFI) and the transaction may be refunded to the sender if the RFI goes unanswered for 24 hours. For approved customers, compliance can open a non-blocking RFI while the customer keeps full access, typically for periodic reviews.

How long does verification take?

It takes about 60 seconds for an automated standard check and 3 hours to 1 business day for a manual one. Real timelines are longer when documents are poor or an RFI opens.

StepTypical timeWhat stretches it
KYC StandardAbout 60 secondsNeeds manual review, stays verifying
KYC Enhanced3 hours to 1 business dayMissing source of funds or proof of address
KYB Standard3 hours to 1 business dayLayered ownership, missing owner documents
RFI responseSet per request; see the RFI docs for the deadlineSlow customer replies, one open RFI at a time
Transaction on holdUp to 30 days to resolveUnanswered RFI after 24 hours may mean a refund

Development instances approve customers automatically, so test the rejection and RFI paths on purpose. The sandbox guide lists how.

Should you build or buy compliance?

Buy it when compliance is not your product, and build only the parts that are unique to you. A hybrid works for most teams: the payment API verifies and screens, and you own your program, policies and customer data collection.

QuestionBuild in-houseBuy inside the payment API
Time to launchLonger: vendors, policies and review staff to set upShorter, because verification is an API call
Review staffYou hire and train analystsThe provider's compliance team reviews
CoverageYou choose and integrate each vendorIncluded in one flow
Your obligationsYoursStill yours, even with a provider

A provider does not take over your program duties. BlindPay's docs say you collect the data and BlindPay verifies it, and if your customers act as money transmitters they must register their own end customers. See automated vs manual onboarding and stablecoin payout compliance for the responsibility split. For how this fits platform choice, see how to evaluate a payments API.

How BlindPay does it

BlindPay handles customer creation and verification inside the API. Every payment flows through a customer that has completed KYC or KYB, and the compliance layer covers KYC, KYB, sanctions screening, Travel Rule checks and requests for information in the same flow. See BlindPay compliance.

  1. You create the customer with type individual or business and kyc_type standard or enhanced.
  2. The customer accepts the terms of service on app.blindpay.com.
  3. BlindPay verifies. Status moves from verifying to approved or rejected, or to compliance_request when an RFI opens.
  4. You receive a customer.update webhook on each change.
  5. Limits apply by tier: per transaction $10,000 for KYC Standard, $30,000 for KYB Standard and $50,000 for KYC Enhanced, raised on request with more documents.

BlindPay combines a monthly plan (platform access) with per-transaction fees that vary by rail and network and are disclosed only in the live quote before execute. Plans include a compliance-check allowance, 500 on Basic as of November 2026, and the other plans are listed on the pricing page. For corridor use, see sending payments to Latin America.

A launch checklist for KYC and KYB

Work through this list before you take live money.

  1. Decide which customer types you serve: individuals, businesses or both.
  2. List the countries you will serve and check them against your provider's tiers.
  3. Design the onboarding form around the required fields so reviews do not stall.
  4. Add document guidance: whole document, no screenshots, no screen photos.
  5. Handle every status in code: verifying, approved, rejected, compliance request and approved with an open RFI.
  6. Subscribe to status webhooks and verify their signatures.
  7. Build an RFI screen so a customer can answer within the deadline.
  8. Create a new customer for a rejected one, with corrected fields, instead of editing in place.
  9. Write down who owns sanctions rescreening, monitoring and recordkeeping.
  10. Test rejection, RFI and on-hold paths in development before production.

For platform design, see payment infrastructure for fintechs, payroll and remittance and custodial vs non-custodial payment processing.

Methodology and sources

Checked in November 2026. BlindPay figures come from its docs, and legal figures from the cited regulations.

This article is for general information only and is not legal, tax, or compliance 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.