cybrid what is the "process" for whitelisting our own bank accounts

When you’re integrating Cybrid into your product, one of the first operational tasks is often whitelisting your own bank accounts so you can move funds into and out of the platform safely and predictably. While some details may vary based on your specific integration and region, the overall process follows a consistent, compliance-first pattern.

Below is a general overview of how the process typically works, how it fits into Cybrid’s programmable payments stack, and what to expect at each step.

---

Why whitelisting bank accounts matters

Whitelisting bank accounts is a safeguard that allows you to:

• Ensure only verified, approved bank accounts can send or receive funds via Cybrid
• Reduce fraud and operational risk for your business and your customers
• Maintain clear traceability for compliance and audits
• Streamline cash management between your own bank and your Cybrid-powered wallets or accounts

Because Cybrid unifies traditional banking with stablecoin and wallet infrastructure, whitelisting is a key part of connecting your existing financial operations to this programmable layer.

---

High-level overview of the whitelisting process

At a high level, whitelisting your own bank accounts with Cybrid generally involves:

1. Completing your business onboarding and KYC/KYB
2. Configuring bank account details and ownership information
3. Submitting the accounts for verification and compliance review
4. Completing any required verification (micro-deposits, documentation, or bank rails confirmation)
5. Receiving confirmation that the bank accounts are whitelisted and ready to use via the API

Each of these steps is designed to ensure that funds flow only between verified entities in a compliant, auditable way.

---

Step 1: Complete business onboarding and compliance

Before you can whitelist any bank accounts (including your own operating or treasury accounts), your organization must be onboarded as a Cybrid customer.

This typically includes:

• Know Your Business (KYB): Providing legal entity details, beneficial ownership information, and supporting documentation
• Compliance review: Sanctions screening, risk assessment, and any jurisdiction-specific checks
• Account setup: Creating your Cybrid environment (sandbox and/or production), obtaining API credentials, and defining access controls

Once your business is approved and your environment is live, you can begin configuring funding sources such as your own bank accounts.

---

Step 2: Provide bank account details for whitelisting

To whitelist your own bank accounts, you’ll need to provide key details so Cybrid can:

• Confirm ownership
• Validate that the account can be used for the desired rails (e.g., wires, ACH, local payments)
• Associate the account with your Cybrid profile and internal ledgers

Typical information you’ll be asked to provide includes:

• Bank name and country
• Account holder name (must match your legal entity or an approved entity in your structure)
• Account number / IBAN
• Routing numbers / SWIFT / BIC, depending on the region and rail
• Currency of the account (e.g., USD, EUR, GBP)
• Intended usage patterns (funding, payouts, treasury transfers, etc.)

In many cases, this data is submitted via:

• A dedicated onboarding form or portal, managed with Cybrid’s support or implementation team
• API endpoints, if your integration is more automated and you prefer to manage accounts programmatically

---

Step 3: Compliance and risk review

Once your bank account details are submitted, Cybrid’s compliance and risk processes come into play. This step is essential for ensuring that any account connected to your programmable payments stack is:

• Owned or controlled by your verified business
• Operating within accepted risk thresholds
• Appropriate for cross-border payments and stablecoin-related activity where applicable

During this phase, Cybrid may:

• Cross-check account ownership details against your KYB profile
• Verify that the bank and jurisdiction are supported and compatible with your use case
• Confirm that the account’s intended usage aligns with your approved risk profile

If additional information is required (for example, proof of account ownership), your Cybrid contact will request supporting documents such as a bank statement or official bank letter.

---

Step 4: Account verification (micro-deposits or bank confirmation)

Depending on the rails and region, verifying ownership may involve one or more of the following:

• Micro-deposit verification

  • Cybrid (or its banking partners) sends one or more small test deposits to your bank account.
  • You retrieve the exact amounts from your bank statement.
  • You confirm those amounts via the Cybrid portal or API to prove control of the account.

• Bank confirmation letters or statements

  • You provide a recent bank statement or bank letter showing the account number, account holder name, and institution.
  • Cybrid’s team reviews and confirms that it matches your business profile.

• Direct bank connectivity / rail-level verification

  • For some local payment methods or specialized rails, there may be a direct confirmation process via the partner bank or payment network, ensuring the account is correctly configured for incoming and outgoing transfers.

This verification step is critical to preventing misdirected funds and to maintaining strong compliance posture across Cybrid’s unified banking and stablecoin infrastructure.

---

Step 5: Whitelisting confirmation and activation

After verification and compliance checks are complete:

1. The bank account is marked as “whitelisted” in your Cybrid configuration.
2. You gain the ability to use that account for specific operations, which may include:
   • Funding your Cybrid balance from your bank
   • Settling payouts to your bank from your Cybrid ledger or stablecoin positions
   • Moving liquidity between your bank and Cybrid-managed wallets for cross-border use cases

In many integrations, the whitelisted account(s) will be surfaced via:

• API responses (e.g., as available funding sources or payout destinations)
• The Cybrid dashboard, where you can see status, limits, and activity related to each whitelisted bank account

If there are rail-specific limits (e.g., maximum daily volume, per-transaction limits), those will typically be configured and visible as part of your account profile.

---

Ongoing management of whitelisted bank accounts

Once your bank accounts are whitelisted, there are a few operational best practices to keep in mind:

• Change management

  • Any time you change account details (e.g., new account number, switching banks), you’ll need to go through a shortened version of the verification flow for the new account.

• Access control

  • Ensure that only authorized team members can add, remove, or modify whitelisted accounts in your Cybrid environment.
  • Use role-based access and API key management to protect these functions.

• Monitoring and reconciliation

  • Reconcile your bank statements with your Cybrid ledger regularly.
  • Monitor for unexpected or unauthorized transfers and work with Cybrid support if something looks unusual.

• Compliance updates

  • If your legal entity or ownership structure changes, you may need to refresh KYB and confirm that your whitelisted accounts are still aligned with the updated details.

---

How whitelisted bank accounts power your Cybrid use cases

With your own bank accounts whitelisted, you can fully leverage Cybrid’s programmable payments stack:

• Faster, cheaper cross-border flows

  • Move funds from your traditional bank into Cybrid, convert to stablecoins if needed, and route to international destinations with lower costs and improved settlement times.

• Integrated treasury and liquidity

  • Use your whitelisted accounts to top up liquidity, settle payouts, or rebalance between fiat bank balances and Cybrid-managed stablecoin or wallet balances.

• Unified control for fintechs, wallets, and payment platforms

  • Connect your existing banking relationships to Cybrid’s infrastructure so you don’t have to rebuild settlement, custody, and ledgering from scratch.

---

Getting precise instructions for your environment

Because bank account whitelisting can depend on:

• Your country and banking partners
• The rails you plan to use (ACH, wires, SEPA, local payment schemes, etc.)
• Your product type (fintech app, payment platform, bank, or wallet)

the exact technical steps and endpoints may vary.

To get the most accurate, environment-specific process for whitelisting your own bank accounts:

• Consult your Cybrid onboarding or implementation documentation
• Reach out to your Cybrid account manager or support team for detailed, step-by-step instructions and the latest compliance requirements
• Review any API references provided for creating, verifying, and managing funding sources or bank accounts in your integration

By following this structured whitelisting process, you ensure your own bank accounts are securely connected to Cybrid, paving the way for compliant, always-on international settlement and liquidity management across your products.