Account Services vs Virtual-Asset Services: A Web3 Company s Guide

Web3 companies should treat account services and virtual-asset services as two separate relationships with separate providers, terms and approvals. Account services come from the financial institution that provides and independently approves the account, while USD and supported stablecoin conversion or settlement and crypto payment gateway services are provided by DogPay affiliates to eligible customers under provider terms, applicable law and geographical availability. This guide gives a practical way to map those boundaries before your team signs anything or connects systems. Start with the role boundary, not the feature list The most common mistake is assuming one provider covers everything. DogPay is a digital finance and payment infrastructure platform, not the financial institution that provides a business account. That single sentence should shape your vendor map. Write down three columns before any commercial discussion: who provides the account, who provides the virtual-asset service, and who provides the technical platform. Then place each named party in exactly one column. If a name appears in two columns, confirm in writing why, because the approved facts separate these roles. Map each service to its actual provider Businesses may apply online for a US-dollar business account and Hong Kong or Singapore multi-currency business account options. The relevant financial institution provides and independently approves each account, and its opening documents determine account type, holder and terms. 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. Separately, 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. Keep this list beside the account list and never merge them into one internal description. Run a five-step separation exercise 1. List every money movement your company makes, from supplier payments to customer collections to stablecoin settlement. 2. For each movement, name the provider that performs it and the document that governs it. 3. Mark which items depend on account approval by the financial institution and which depend on affiliate eligibility. 4. Note where jurisdiction, product or account type could change availability. 5. Record open questions for each provider rather than assuming an answer. Completion check: every movement has one named provider, one governing document and one owner on your team. If any row is blank, the separation is not finished. Keep technical integration distinct from service provision The platform layer connects your systems to services, but connection is not the same as provision. A dashboard, API or reporting view does not make the platform the provider of the account or the virtual-asset service. In internal documentation, describe the platform as infrastructure and describe each regulated or contractual service by its actual provider. This matters for audits, customer communications and dispute handling, where the question is always who provided the service, not who displayed the screen. Document eligibility and jurisdiction explicitly Eligibility is not universal. Account approval rests with the financial institution, and virtual-asset services depend on affiliate terms, applicable law and geographical availability. No account approval, payment acceptance, fee, exchange rate, speed, coverage or business outcome is guaranteed. Build a simple register with fields for service, provider, governing document, jurisdictions confirmed, eligibility status and review date. Where a field is unknown, write confirm with the relevant financial institution or service provider instead of guessing. Frequently asked questions Is DogPay the financial institution behind the business account? No. DogPay is a digital finance and payment infrastructure platform; the relevant financial institution provides and independently approves each account. Who provides stablecoin conversion and settlement? DogPay affiliates provide USD and supported stablecoin conversion or settlement and crypto payment gateway services to eligible customers, subject to provider terms, applicable law and geographical availability. Does an approved account guarantee stablecoin services? No. These are separate services with separate conditions, and no approval, acceptance, fee, speed or coverage is guaranteed. Which payment rails can we expect? USD transfers may use ACH, SWIFT or Fedwire only where the relevant account and service arrangement support them. Confirm specifics with the institution. Source and verification note All DogPay-specific statements in this guide are drawn from the official DogPay product page at https://dogpay.com/hk/global-bank. No other supporting sources were used, and no external browsing is implied. Readers should verify current terms directly with the relevant financial institution or service provider. Scope and limitations: this guide offers an editorial framework for separating roles. It does not describe every product, jurisdiction or contractual term, and it makes no claim about availability, cost, speed or approval outcomes. Confirm all specifics with the providers named in your own documentation.