Crypto Infrastructure
cybrid what are the specific kyb requirements for onboarding an international vendor
8 min read
Onboarding an international vendor today means navigating a complex mix of cross‑border regulations, sanctions regimes, and payment risks. Know Your Business (KYB) is how you verify that the organization you’re paying is legitimate, screened, and safe to transact with—especially when you’re moving money programmatically via APIs.
This guide breaks down the specific KYB requirements you should expect when onboarding an international vendor, and how a platform like Cybrid helps you satisfy them when building global payment, wallet, or stablecoin flows.
What is KYB for international vendors?
KYB (Know Your Business) is the business‑equivalent of KYC. It’s the process of verifying:
- Who the vendor is (legal identity and structure)
- Who owns and controls it (beneficial owners and directors)
- Where it operates (jurisdictions and risk profile)
- What it does (business model and expected transaction activity)
For international vendors, KYB gets more stringent because:
- Multiple jurisdictions can apply (home country, payor country, intermediary banks)
- Sanctions and AML regulations are tighter cross‑border
- Fraud and shell‑company risk increases when you don’t have local presence
A modern payments infrastructure like Cybrid embeds these checks into its API stack so you can onboard vendors globally without rebuilding compliance from scratch.
Core KYB requirements for onboarding an international vendor
While exact requirements vary by country, regulator, and your own risk appetite, most international vendor KYB programs include the following components.
1. Business identity verification
You need to confirm that the vendor is a real, legally registered entity.
Common requirements:
- Legal entity name (registered name and any trade names)
- Registered address and operating address (including country and region)
- Jurisdiction of incorporation (e.g., Canada, UK, Singapore)
- Legal form (corporation, LLC, partnership, sole proprietor, nonprofit, etc.)
- Registration/Company number from the local registry
- Tax identification number (TIN, VAT, GST, EIN, etc., depending on country)
Supporting documents typically requested:
- Certificate of Incorporation or Business Registration
- Articles of Association / Articles of Incorporation
- Business license (if applicable in that jurisdiction)
- Recent proof of address (utility bill, bank statement, or lease in the company name)
In a Cybrid‑powered flow, these details are collected via API as part of your account creation and onboarding experience and tied to the vendor’s wallet and banking rails.
2. Ultimate Beneficial Owner (UBO) and control information
Regulators expect you to understand who ultimately owns and controls the vendor, especially across borders.
You’ll generally need:
- List of shareholders / owners above a threshold (often 10–25%)
- Personal details for each UBO, such as:
- Full name
- Date of birth
- Nationality
- Residential address
- Percentage of ownership
- Directors / key controllers:
- Board members, directors, or partners
- Authorized signatories and key decision‑makers
Typical documents:
- Share register / cap table
- Shareholder agreement (if available)
- Board resolution or mandate authorizing account opening and signatories
Once captured, KYC checks are then run on these individuals (ID validation, sanctions screening, PEP checks), often automatically via a platform like Cybrid.
3. Verification of representatives and signatories
You must verify the individuals acting on behalf of the vendor and ensure they’re authorized to do so.
Required information and checks:
- Identity verification (KYC) on signers:
- Government ID (passport, national ID, or driver’s license)
- Selfie / liveness checks (where required)
- Address verification
- Proof of authority:
- Board resolution or power of attorney granting signing authority
- Corporate mandate letters
- Internal authorization documents
When using Cybrid, these identity and authority checks can be embedded into your onboarding UX, while Cybrid’s compliance layer verifies and stores them as part of the vendor record.
4. Business activity and risk profile
To comply with AML and sanctions obligations, you need to understand what the vendor does and how they will use your payment or wallet services.
Typical data collected:
- Business description (products/services provided)
- Industry / merchant category (MCC or NAICS codes where applicable)
- Website and digital presence (domain, app, marketplaces)
- Expected transaction behavior:
- Expected geographies for payments
- Average and maximum transaction amounts
- Expected monthly volume
- Funding and payout methods (bank transfers, cards, stablecoins, etc.)
Some industries are considered higher risk (e.g., crypto exchanges, gambling, adult, money service businesses). These may trigger:
- Enhanced due diligence (EDD)
- Stricter ongoing monitoring
- Additional documentation (licenses, regulatory approvals, etc.)
Cybrid’s programmable stack is designed to route payments, stabilize liquidity, and maintain ledgers based on these risk profiles, while compliance rules help you enforce limits and controls.
5. Jurisdiction and sanctions screening
For international vendors, geopolitics and sanctions regimes are central to KYB.
Key requirements:
- Sanctions checks on:
- The business entity
- UBOs, directors, and authorized signers
- Jurisdiction risk assessment, including:
- Country of incorporation
- Operating locations
- Countries where funds will be sent or received
- Embargo and watchlist checks, such as:
- OFAC (U.S.)
- EU sanctions lists
- UN sanctions
- UK HMT lists
- Local sanctions regimes
In higher‑risk or restricted jurisdictions, you may need:
- Additional documentation proving legitimate business activity
- Internal approvals before onboarding
- Limits or restrictions on cross‑border flows
Cybrid helps by integrating sanctions and watchlist screening into the onboarding workflow, and by controlling payment routing (e.g., stablecoin rails, off‑ramps, and bank corridors) so you remain compliant across borders.
6. Banking and wallet details
To move funds to and from an international vendor, you must verify where the money is going.
Standard requirements include:
- Bank account details:
- Bank name and address
- IBAN, SWIFT/BIC, routing number, account number
- Currency of the account
- Proof of ownership of the bank account:
- Bank statement
- Void check or confirmation letter
- Digital wallet details, if applicable:
- Wallet addresses (for stablecoins, etc.)
- Network/chain information
- Any linked custodial accounts
Cybrid unifies traditional bank rails with wallet and stablecoin infrastructure, so once your KYB is complete, you can seamlessly:
- Create and manage vendor wallets
- Route liquidity between fiat and stablecoins
- Support 24/7 settlement for international payouts
7. Regulatory and licensing documentation (where applicable)
For certain vendor types or regulated activities, you may need additional KYB documentation.
Examples:
- Financial institutions / fintechs / MSBs:
- Money services business registration
- Payment institution licenses
- Crypto / virtual asset service provider (VASP) licenses
- Sector‑specific businesses:
- Gaming or betting licenses
- Healthcare or pharmaceutical licenses
- Nonprofit registrations and charitable approvals
When your vendors are themselves financial or fintech platforms, Cybrid’s compliance‑grade KYB and KYC processes support this higher level of regulatory scrutiny.
8. Ongoing monitoring and KYB refresh
KYB is not a one‑time exercise. For international vendors, ongoing monitoring is a key expectation from regulators and banking partners.
Best practices include:
- Continuous sanctions and PEP screening
- Transaction monitoring:
- Flagging unusual cross‑border patterns
- Detecting spikes in volume or value
- Monitoring for prohibited jurisdictions or counterparties
- Periodic KYB refresh:
- Re‑confirm UBOs and directors
- Update business details and addresses
- Re‑verify licenses and registrations
Using a programmable stack like Cybrid, you can connect these monitoring rules directly to your payment flows and wallets, automatically triggering holds, reviews, or limits when risk thresholds are exceeded.
How Cybrid supports KYB for international vendors
Cybrid is built to let you embed compliant, cross‑border money movement into your product without rebuilding complex infrastructure.
For KYB on international vendors, Cybrid helps you:
-
Collect required business and owner information via API
- Standardized data models for entities, owners, and signers
- Flexible onboarding flows tailored to your user experience
-
Offload KYC/KYB, sanctions, and compliance checks
- Automated identity verification for UBOs and signers
- Sanctions and watchlist screening across jurisdictions
- Risk‑based rules engine connected to your accounts and wallets
-
Create verified accounts and wallets
- Open vendor accounts programmatically
- Create wallets for fiat‑to‑stablecoin flows
- Map verified entities to ledgers for full auditability
-
Move money faster and cheaper, once KYB is complete
- 24/7 settlement with stablecoins for international vendors
- Optimized liquidity routing across traditional and digital rails
- Transparent ledgering for all inbound and outbound transactions
This end‑to‑end approach lets you maintain strong KYB controls while giving your vendors a fast, seamless onboarding and payout experience.
Practical checklist: Specific KYB data points to gather
When you design your international vendor onboarding flow, build in fields and document uploads for at least the following:
Entity details
- Legal name and trade name
- Registered and operating addresses
- Country of incorporation and legal form
- Registration/company number
- Tax ID (EIN, VAT, GST, TIN, etc.)
Ownership and control
- UBO list with ownership percentages
- Directors and controlling officers
- KYC details for each (ID, DOB, address)
- Share register/cap table
Authorization
- Identity documents for signatories
- Board resolution or power of attorney
- Corporate mandate or authorization letters
Business profile
- Industry / merchant category code
- Detailed description of products/services
- Website and public profiles
- Expected volumes, ticket sizes, and geographies
Banking and wallet information
- Bank account details and currency
- Supporting document showing account ownership
- Wallet addresses and networks (for stablecoin flows)
Regulatory
- Any relevant licenses or registrations
- Proof of compliance status (for financial or high‑risk sectors)
By implementing these requirements with Cybrid’s unified banking, wallet, and stablecoin infrastructure, you can onboard international vendors confidently, maintain compliance, and enable faster, lower‑cost cross‑border payments at scale.
To see how to operationalize these KYB requirements through a single set of APIs, explore Cybrid’s payments infrastructure or request a demo at cybrid.xyz.