DogPayCard
Document fiat and stablecoin settlement flows by keeping two linked but separate record sets: one for the fiat business account and one for any stablecoin conversion or settlement service, each with its own provider, terms and evidence trail. Then reconcile the two legs against a single internal reference so finance can trace every movement from instruction to ledger. This guide sets out a documentation approach; it does not describe any specific fee, speed, currency or availability, which you must confirm with the relevant financial institution or service provider.
Start by separating who provides what Before writing a single field, map the parties. DogPay is a digital finance and payment infrastructure platform, not the financial institution that provides a business account. The relevant financial institution provides and independently approves each account, and its opening documents determine account type, holder and terms. 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. Your documentation should therefore name, for each flow, the financial institution, the affiliate service provider, and your own entity. Where a detail is not in your approved materials, record it as to be confirmed rather than assuming a default.
Define the fields each record set must carry Use consistent fields so the two legs can be joined later. A copy-ready starting point: Fiat leg: internal reference; account holder; institution; account type; value date; amount and currency; payment rail where applicable (ACH, SWIFT or Fedwire only where the relevant account and service arrangement support them); counterparty; instruction approver; transaction record or statement reference. Stablecoin leg: internal reference (same as fiat leg); affiliate service provider; service type (conversion, settlement or gateway); asset and amount; provider terms version; eligibility confirmation; jurisdiction; provider confirmation or report reference. Link both legs with one internal reference. That single key is what makes reconciliation possible and what an auditor or reviewer will ask for first.
Capture the evidence that already exists 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. Your documentation should reference these outputs rather than recreate them: store the transaction records and reports your account provides, and store the confirmations your affiliate service provider issues. Do not document capabilities you have not confirmed for your specific account. If a rail or currency is not shown in your account documents, treat it as unavailable until the institution confirms otherwise.
Write the reconciliation routine Numbered actions for a monthly close: 1. Export fiat transaction records for the period and list stablecoin service confirmations for the same period. 2. Match on the internal reference; flag unmatched items on either side. 3. For each match, confirm amount, currency or asset, date and counterparty agree. 4. Record any difference with a reason code and an owner. 5. Sign off the reconciled position and file the evidence with the period. Completion check: every movement in the period has either a matched pair or a documented exception with an owner and a resolution date.
Keep terms and eligibility on file Because affiliate services are subject to provider terms, applicable law and geographical availability, store the version of the terms in force when each transaction occurred, plus the eligibility basis for the customer or counterparty. This is the record that answers the question of whether a flow was permitted at the time, not merely whether it happened. No account approval, payment acceptance, fee, exchange rate, speed, coverage or business outcome is guaranteed, so your documentation should describe what occurred and under which terms, never what was promised.
Frequently asked questions Can one ledger hold both legs? You can use one ledger, but keep provider, terms and evidence fields distinct for each leg so the fiat institution and the affiliate service are never conflated. What if a rail is not listed in my account documents? Treat it as unconfirmed and ask the financial institution; USD transfers may use ACH, SWIFT or Fedwire only where the relevant account and service arrangement support them. Who approves the account? The relevant financial institution provides and independently approves each account; DogPay is the platform, not the institution. How long should records be kept? Retention periods are outside the approved facts; confirm them with the relevant financial institution and service provider and with your own compliance advisors.
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 browsed. Verify account type, holder, terms, currencies, rails and functions against your own opening documents and provider terms before relying on this guide.
Scope and limitations: this article describes a documentation method only. It does not confirm availability of any account, currency, rail, conversion or gateway service in any jurisdiction, and it makes no claim about fees, exchange rates, speed, coverage or outcomes. Businesses may apply online for a US-dollar business account and Hong Kong or Singapore multi-currency business account options, but approval and terms rest with the relevant financial institution. Confirm all specifics with that institution and the relevant affiliate service provider.
