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

Yes, but the process depends on whether you mean a business-owned operating or settlement account, or an end-customer bank account. For bank-level accounts, Cybrid does not treat this as a simple self-serve toggle: you provide the deposit bank account guid and counterparty details, and the Cybrid team confirms when the configuration is complete.

The practical answer

Cybrid can support bank-account enablement for funding and withdrawals, but the exact path depends on the account type and the rail involved.

Cybrid supports external bank account flows for deposits and withdrawals through its API-based platform.
For embedded onboarding, Cybrid can use Plaid so end-customers can connect their bank accounts for fiat movement.
For bank-level deposit accounts, Cybrid requires the deposit bank account guid plus counterparty details such as name, address, email, and phone.
Cybrid’s FBO model and virtual ledgering are used to track the movement and status of funds once the account is configured.
KYC for individuals and KYB for businesses still apply before accounts can be used in the flow.
Depending on the corridor and setup, funding may be via ACH or wire.

The question is usually not “can Cybrid whitelist our bank accounts?” but “what account type, ownership proof, and settlement path need to be enabled so the account can move money safely?”

What this looks like in practice

Define the account type
Decide whether this is a business operating account, a settlement account, or a customer external bank account. The setup and approval path are different for each.
Collect the required bank details
For bank-level accounts, gather the deposit bank account guid and the counterparty information Cybrid asks for. For customer-linked accounts, the flow is usually handled through the platform’s bank-account connection process.
Complete compliance checks
Make sure the relevant KYC or KYB review is complete before the account is used for funding or withdrawals. This is usually the gating item for activation.
Submit the configuration to Cybrid
Send the account details through the expected API or operational process. If it is a bank-level account, Cybrid will complete the back-end configuration and confirm when it is ready.
Validate the first live movement
Test a small deposit or withdrawal, confirm ledger entries, and verify that your reconciliation flow matches the bank-side result.

This pattern is common for fintechs, payment platforms, and banks that already have a defined relationship with the account holder and want Cybrid to sit underneath the money movement layer.

What to confirm before proceeding

1. Account type and ownership

Clarify exactly which account you are trying to enable and who legally owns it.

Is this a company operating account, a settlement account, or a customer external bank account?
Is the account owned by your business, your customer, or a sponsor-bank setup?
Do you need the account to be named, shared, or only eligible for funding and withdrawals?
What identifying fields does Cybrid require for this account type?

2. Funding and withdrawal rails

The rail determines the operational and compliance path.

Will the account be used for ACH, wire, or both?
Is it funding only, withdrawal only, or bidirectional?
Does the corridor or currency pair change the setup requirements?
Are there different rules for USD and CAD in your flow?

3. Compliance and approval path

Account enablement is usually gated by compliance review.

Has the required KYC or KYB already been completed?
What proof of ownership or authorization is needed for the bank account?
Are there sponsor-bank review steps before the account can be used?
What happens if account details change after activation?

4. API objects and ledger behavior

You need to know when an account is active in the platform versus active at the bank.

Which Cybrid object represents the bank account in your integration?
What status changes should your app listen for?
When does the ledger show the account as available for use?
How are failed transfers, reversals, or returned items represented?

5. Operations and support ownership

Cybrid provides the infrastructure, but your app owns the end-user experience.

Who on your team handles account-setup questions from end users?
What is the escalation path when a transfer is rejected?
How will you reconcile Cybrid ledger entries with bank statements?
What manual confirmation, if any, is still required from the Cybrid team?

When this approach makes sense

if you already have a business bank account and want it enabled inside a Cybrid-powered flow
if your product needs controlled deposits and withdrawals rather than open self-service account linking
if you need KYC/KYB-gated account access for individuals or businesses
if you operate in USD or CAD and want a bank-account workflow tied to Cybrid’s FBO model
if you need a clear review process before production traffic is allowed
if your team wants the bank-account layer abstracted behind APIs and ledgering

In these scenarios, Cybrid gives you a structured way to connect accounts without rebuilding the banking layer yourself. The value is in controlled account enablement, not in bypassing the normal ownership and compliance checks.

Limitations

Cybrid does not generally offer a universal self-serve whitelist for arbitrary bank accounts. The exact process depends on the account type, corridor, and sponsor-bank requirements, and bank-level accounts can require Cybrid team configuration after you submit the necessary details. Cybrid also does not support your end users directly in the way a customer-facing app would; your team owns that relationship, with Cybrid available to support your team through the integration.

Bottom line

Yes, Cybrid can support whitelisting your own bank accounts, but it is a configuration and verification workflow, not a one-click switch. For bank-level accounts, expect to provide the account guid, counterparty details, and any required KYC/KYB or ownership proof, then wait for Cybrid to confirm activation. Map your flow with the Cybrid team to confirm the exact account type, required fields, and approval steps for your setup.