Global accounts. Receive and send payments.

Embed global accounts for receiving and sending payments into your platform. Connect named Virtual Accounts, eligible fiat–crypto settlement, cards, wallets and acquiring through DogPay.

Request API Access
  • USD
  • EUR
  • GBP
  • HKD
DogPay

Named Virtual Accounts for individuals and businesses

KYCKYBKYT
Cross-border collection and payouts
Fiat–crypto settlement on eligible routes

Account type, currency and rail availability must be checked together. These options do not imply every combination is available.

  • FinCEN MSB
  • FINTRAC MSB
  • Hong Kong TCSP

Entity-specific disclosures, not a bank charter. DogPay is not a bank; see the applicable entities and service scope.

Read VA docsSee compliance

The right account for each customer.

Choose an onboarding path. Check available routes before you build.

  • Named Virtual Accounts for individuals and businesses
  • Cross-border collection and payouts
  • Fiat–crypto settlement on eligible routes
Global receiving and payment accounts. Built into your product.

DogPay provides account and payment infrastructure that platforms can integrate into their own customer journeys. Named Virtual Accounts, transfers and eligible fiat–crypto flows connect through partner arrangements. Account issuance, permissions and availability depend on the customer, corridor and compliance review. This service does not provide a banking licence or replace your own regulatory obligations.

  • Named Virtual Accounts for individuals and businesses
  • Cross-border collection and payouts
  • Fiat–crypto settlement on eligible routes
  • No claim of US deposit insurance or a bank charter

Individual accounts

A named account journey for individuals, with identity checks and account-opening documents.

  • KYC and proof of address
  • FATCA and source-of-funds documents
  • Eligibility checks before the VA application

Platform currency options

  • USD
  • EUR
  • GBP
  • HKD

Account type, currency and rail availability must be checked together. These options do not imply every combination is available.

Explore the details

Account options include individual and business onboarding, with currency and bank routing determined by current availability. USD, EUR, GBP and HKD are disclosed platform options; SGD also appears in enterprise account configuration. This is not a currency-by-rail guarantee. Query current supported routes and confirm the account type, receiving currency and payout requirements during onboarding.

  • Individual and business account paths
  • USD / EUR / GBP / HKD platform options
  • SGD subject to enterprise route confirmation
  • Query Supported Banks v2
  • Proof of Account / COA where available

Proof of Account (COA)

Account confirmation documents are available for eligible VAs. Confirm the issuing route, format and third-party acceptance requirements.

Query supported routes

Receive. Pay out. Reconcile.

Bank transfers and digital asset settlement, connected to the account lifecycle.

Asynchronous account and transaction updates

entity.status.updateva.createva.update
DogPay
SWIFT / SEPA

SWIFT and SEPA, subject to route eligibility

ACH / FPS

ACH / FPS only where the selected route supports them

Eligible fiat ↔ crypto settlement
Follow the account lifecycle

Build collection, payouts and reconciliation around the routes approved for your account. SWIFT and SEPA are disclosed payment networks. Other local rails, including ACH and FPS, depend on the corridor and partner arrangement. Eligible fiat–crypto conversion can connect account funds with digital asset flows. Fees, cut-offs, conversion rates and settlement timing are confirmed for each route.

entity.status.update
Verification status
va.create
Application registered
va.update
Account details issued or updated

Application submission is not account approval. Use transaction event documentation for deposit and payout status; verify signatures and handle repeated notifications.

Two ways to partner.

Match API access and responsibilities to how your business operates.

Explore the details

Choose the partnership model before defining the integration. A licensed PSP operates within its own approved framework; an agent or channel partner focuses on customer introduction and application support. Fund handling, API permissions, fees and responsibilities are set in the partnership agreement. Neither model removes applicable legal duties or guarantees account approval for downstream customers.

  • Licensed PSP / Institution loop
  • Agent & Channel loop
  • Contract-defined funds and compliance responsibilities

Licensed PSP / Institution

Your role
Serve downstream customers within your own approved framework.
Funds & compliance
Operate under your applicable authorisations and agreed partner arrangements.
API scope
Account applications, permitted payment instructions and reconciliation.
Commercial model
Agreed fee configuration and downstream pricing.

An agent still has agreed documentation, customer-support and compliance responsibilities. Permissions are granted under the selected model.

Compare both partnership models
Licensed PSP / InstitutionAgent & Channel
Your roleServe downstream customers within your own approved framework.Your roleIntroduce customers and support application submission.
Funds & complianceOperate under your applicable authorisations and agreed partner arrangements.Funds & complianceFunds are handled through DogPay’s service arrangements and licensed institutions; agents do not pool customer funds.
API scopeAccount applications, permitted payment instructions and reconciliation.API scopeApplication tracking and agreed commission queries or settlement.
Commercial modelAgreed fee configuration and downstream pricing.Commercial modelContract-defined referral and commission arrangements.

Know the customer. Then open the account.

KYC / KYB for onboarding. KYT for transaction risk.

  1. Create the entity

    Select the individual or business workflow.

  2. Complete verification

    Upload documents; complete KYC/KYB and relevant biometric checks.

  3. Check eligibility

    Resolve RFI and confirm the applicable status and canApplyVa checks.

  4. Apply and track

    Submit the VA application; follow va.create and va.update.

Explore the details

Onboarding covers identity or business verification, relevant supporting documents and partner review. FATCA and source-of-funds evidence form part of the account application requirements. Key business personnel may need biometric verification. Track additional-information requests and review outcomes before submitting an account application. Applicable entity status and canApplyVa checks depend on the individual or business workflow.

  • Entity creation and document upload
  • KYC / KYB and relevant biometric checks
  • FATCA and Source of Funds
  • RFI handling and eligibility status
  • KYT and ongoing transaction screening

FinCEN MSB, FINTRAC MSB and Hong Kong TCSP apply only to the entities and scopes disclosed on our Licenses page. MSB registration and TCSP licensing do not constitute a bank charter or deposit insurance.

See compliance
Evaluate the integration before launch.

Separate environments. Explicit access. Documented workflows.

Start with the sandbox, then apply separately for production access after integration checks. Configure production IP allowlisting and HTTPS webhooks. Test document submission, eligibility handling, asynchronous account states and transaction reconciliation against your intended scenario. The documentation provides a concrete evaluation path without relying on unverified account counts, transaction volumes or a public partner-bank logo wall.

  • Separate sandbox and production accounts
  • Production API access approval
  • Production IP allowlisting
  • HTTPS webhooks and signature verification

Build from the actual workflow.

Compare the partnership models, prepare the required documents and follow the matching VA onboarding guide.

Accounts are the starting point.

Add cards, wallets and acquiring on the same DogPay platform.

Your product. A clear operating model.
Your businessDogPay & partners
Brand, customer relationships and experienceVA application and partner connectivity orchestration
Pricing within the agreed commercial modelAgreed fee tools, reporting and reconciliation
Your scenario rules and regulatory obligationsKYC/KYB workflow tools, status events and review coordination
Customer support and integration logicConnections to eligible wallet, card and payment services

Partner banks and compliance reviewers determine account acceptance and route availability. No automatic approval or unrestricted bank access is implied.

Explore the details

Plan Virtual Accounts and cross-border fund flows alongside card issuing, wallets and payment services. Each service has its own permissions, onboarding requirements and operational scope. Use the relevant APIs and confirm balance transfers and settlement routes. A shared platform does not mean one credential, one balance or automatic access to all products.

  • BaaS: Virtual Accounts and fund flows
  • CaaS: card program integration
  • WaaS: crypto wallet services
  • Payment: acquiring and payment processing
Built for cross-border business.

Fintechs, marketplaces, PSPs, Web3 platforms and cross-border merchants.

Explore collection, payouts and eligible stablecoin–fiat settlement for platforms serving international customers, including use cases involving Nigeria and Latin America. These markets describe commercial scenarios, not local banking licences or clearing membership. Confirm customer eligibility, payer and beneficiary geography, permitted activities and available settlement routes before committing to a launch plan.

  • Fintech and embedded account experiences
  • Marketplace and PSP collections and payouts
  • Web3 fiat–crypto onboarding and settlement
  • Nigeria and Latin America cross-border use cases

Before you integrate

What does DogPay BaaS provide?

Virtual Account onboarding and cross-border fund-flow infrastructure for platforms, with eligible collection, payout and fiat–crypto settlement services.

Is DogPay a bank or a US insured-deposit platform?

No. DogPay is not presented as a bank or a US deposit-account BaaS provider. No FDIC insurance is claimed. MSB/TCSP disclosures do not confer a bank charter.

Which currencies and rails can we use?

Platform options include USD, EUR, GBP and HKD; SGD requires enterprise route confirmation. SWIFT and SEPA are disclosed networks; ACH/FPS are corridor-dependent. Query current routes and confirm the complete account × currency × rail combination.

How do the PSP and Agent models differ?

Licensed PSPs serve customers under their own approved framework and agreed API permissions. Agents focus on introductions, application tracking and commission arrangements, without pooling customer funds. The agreement defines responsibilities.

Can we connect fiat and crypto settlement?

Yes, on eligible routes. Confirm supported assets, conversion terms, fees and settlement currency. This does not imply every VA supports every wallet or asset.

How does this connect to CaaS?

Account flows can be designed alongside DogPay card programs. Product access, transfer paths, funding requirements and issuer eligibility are confirmed separately.

How long does account opening take?

Timing depends on document completeness, customer and corridor eligibility, RFI and partner review. API integration and approved account issuance are separate milestones; request a project-specific plan.

Are partner banks publicly listed?

This page does not publish a partner-bank list. Use the supported-route API and confirm the available partner arrangement during onboarding; API routing information is not permission to publish partner names.

Can we serve Nigeria or Latin America?

Cross-border collection, payouts and stablecoin–fiat use cases can be discussed subject to corridor, customer and partner eligibility. DogPay does not claim local central-bank licensing or local clearing-bank status here.

Can we obtain Proof of Account?

COA support is available for eligible Virtual Accounts. Confirm the selected route, document format and acceptance requirements before relying on it for a third-party platform.

Build your global payment account journey.

Start with your customer markets, partnership model and funding routes. Confirm the fit before you build.

Quick StartPartnership & onboarding help