DogPayCard
Web3 companies should treat the business account and the virtual-asset service as two separate relationships with separate providers, terms and approvals. DogPay is a digital finance and payment infrastructure platform, not the financial institution that provides a business account, and its affiliates provide USD and supported stablecoin conversion or settlement and crypto payment gateway services to eligible customers under provider terms, applicable law and geographical availability.
Why the distinction matters in practice
A business account and a virtual-asset service answer different questions. The account answers where funds are held, who the account holder is, and which collection and payment features apply. The virtual-asset service answers how supported stablecoin conversion or settlement and gateway functions are delivered to eligible customers. Blending the two in one internal owner or one contract review creates confusion about who approves what, who sets terms, and who a finance team contacts when something changes. Because the financial institution independently approves each account and its opening documents determine account type, holder and terms, the account side must always be verified against those documents rather than against marketing material.
Step 1: Map each service to its provider
Before any integration work, build a simple register. For the account, record the financial institution named in the opening documents, the account type, the account holder, and the currencies and payment rails the institution confirms for that account. For virtual-asset functions, record that USD and supported stablecoin conversion or settlement and crypto payment gateway services are provided by DogPay affiliates, and note the provider terms, eligibility conditions and geographical availability that apply. Keep the two entries separate even where one platform is the commercial entry point. If any field is unclear, confirm it with the relevant financial institution or service provider rather than inferring it.
Step 2: Separate approvals from enablement
Account approval and service enablement are different gates. The financial institution provides and independently approves each account, and no account approval is guaranteed. Virtual-asset services are subject to provider terms, applicable law and geographical availability, and no payment acceptance is guaranteed either. A practical control is to require two sign-offs internally: one confirming the account opening documents and approved features, and one confirming the affiliate service terms and eligibility. Neither sign-off should be treated as evidence of the other.
Step 3: Write down what the account can actually do
After approval, available account features may include international collections, cross-border payments, currency management, transaction records, reconciliation and reporting. Actual currencies, payment rails and functions depend on the institution, account, product and jurisdiction. USD transfers may use ACH, SWIFT or Fedwire only where the relevant account and service arrangement support them. Record these as confirmed facts per account, not as platform-wide defaults, and revisit the record whenever the institution updates terms.
Step 4: Keep stablecoin flows in their own lane
Stablecoin conversion, settlement and gateway activity should have its own documentation: which affiliate provides it, which customers are eligible, which jurisdictions are in scope, and which provider terms govern it. Do not describe stablecoin capability as a feature of the bank account, and do not describe account features as part of the virtual-asset service. This separation keeps internal reporting, customer communications and due-diligence responses accurate.
Step 5: Run a completion check
You are finished when your register names the financial institution for each account, states the account holder and approved features from the opening documents, separately names the affiliate-provided virtual-asset services and their governing terms, and contains no statement implying guaranteed approval, acceptance, fees, exchange rates, speed, coverage or business outcomes. Any remaining gap should be marked as pending confirmation with the relevant financial institution or service provider.
FAQ
Is DogPay the bank that holds the business account? No. DogPay is a digital finance and payment infrastructure platform, not the financial institution that provides a business account; the institution provides and independently approves each account.
Who provides stablecoin conversion and settlement? USD and supported stablecoin conversion or settlement and crypto payment gateway services are provided by DogPay affiliates to eligible customers, subject to provider terms, applicable law and geographical availability.
Can a Web3 company assume ACH, SWIFT or Fedwire availability? No. USD transfers may use those rails only where the relevant account and service arrangement support them, and actual rails depend on the institution, account, product and jurisdiction.
Does applying guarantee an account or payment acceptance? No. No account approval, payment acceptance, fee, exchange rate, speed, coverage or business outcome is guaranteed.
Source and verification note
This guide relies only on the official DogPay product page at https://dogpay.com/hk/global-bank. No other sources were used or reviewed. Readers should verify account terms with the relevant financial institution and virtual-asset service terms with the relevant provider before relying on any detail.
Scope and limitations
This article describes role separation only. It does not confirm availability of any currency, rail, feature or jurisdiction for a specific business, and it makes no claim about licensing, cost, speed or outcomes. Confirm all specifics with the relevant financial institution or service provider.
