Your brand. Credit and prepaid cards. One connected platform.
Launch white-label virtual and physical card programs with Apple Pay and Google Pay support on eligible programs. Connect card issuance, spending controls and crypto funding with DogPay’s accounts, wallets and acquiring services.
- 50+ API clients
- Apple Pay / Google Pay
- Credit & prepaid
- BIN sponsor relationships + multiple issuers
API client count confirmed as of October 1, 2026. Wallet eligibility, card types and features vary by program, issuer and region.
Make the card yours.
Your design. Virtual and physical cards. Wallet payments your customers already use.
Try your card design
Preview your artwork locally. This illustration is not a card order or an approved production design. Final artwork remains subject to program and network review.
PNG or JPG, up to 10 MB. Your image stays in this browser.
- Apple Pay and Google Pay on eligible programs
- Custom card face and design
- Virtual card issuance via API
Program details
Offer wallet payments where the selected card program is eligible, and customize the card face for your brand. Virtual card issuance is available through the API after the required approvals and funding checks. Physical card production, delivery, design approval and wallet provisioning requirements are agreed for the selected program.
- Apple Pay and Google Pay on eligible programs
- Custom card face and design
- Virtual card issuance via API
- Physical card options with program-specific delivery
- Bulk issuance, limits and freeze controls as documented
Two ways in. One card journey.
Explore crypto wallet deposits and fiat funding through global accounts.
Wallet coverage shown. Card funding assets, conversion and settlement depend on your program.
Wallet assets
- ETH
- USDT
- USDC
- XAUT
- USD
- EUR
- GBP
- HKD
- SGD
Crypto and fiat funding, connected to your card program
Combine multi-chain crypto wallet deposits with fiat bank transfers through eligible DogPay global accounts. Wallet network coverage is listed below; the assets available for card funding, any conversion steps and the card settlement currency depend on your program. Confirm the deposit address, token contract, minimum amount, fees and processing times before transferring funds.
- Ethereum: ETH, USDT, USDC and XAUT
- Base and Arbitrum: ETH, USDT and USDC on each network
- BNB Smart Chain and Polygon: USDT and USDC on each network
- Solana: SOL, USDT and USDC
- Tron: TRX and USDT
- Bitcoin: BTC · Dogecoin: DOGE
Fiat funding through global accounts
Use eligible global accounts to receive fiat bank transfers and support your card funding workflow. Global account options include USD, EUR, GBP, HKD and SGD, subject to account approval and available receiving currencies. Conversion and allocation to a card or budget follow the selected program’s rules; a receiving account does not make every fiat currency directly spendable on every card.
Built around your program.
Credit or prepaid. Partner issuers. Compliance at every stage.
Customer verification
- KYC
- KYC for individual verification
- KYB
- KYB for business verification
Risk screening
- KYA
- KYA requirements confirmed during program design
- KYT
- KYT and ongoing transaction screening
Hong Kong · Singapore · UK · US
Issuing corridors; cardholder eligibility varies by program.
Selected card programs use Flagright as a risk processor; other partners may use alternate stacks depending on the issuing corridor.
Credit and prepaid. Matched to your use case.
DogPay runs white-label card programs across credit and prepaid. Issuing is delivered through BIN sponsor relationships and an aggregated network of card issuers. Program type, corridor and risk stack are matched to your use case during onboarding. Credit terms, funding requirements and eligibility depend on the selected arrangement; access is not automatic.
- Credit and prepaid program options
- BIN sponsor relationships
- An aggregated network of partner issuers
- Program-specific eligibility, terms and risk controls
Issuing program regions: Hong Kong, Singapore, UK and US. These describe program corridors, not an assurance that every resident or business in those markets can obtain every card. Confirm issuer, cardholder eligibility and availability with sales.
Compliance and risk, configured for your program
KYA, KYC, KYB and KYT controls are part of the program workflow, with responsibilities and implementation agreed at onboarding. Individual and business checks, transaction monitoring and ongoing screening address different stages of the lifecycle. These controls do not replace the customer’s own obligations or imply that every issuing corridor uses the same processing stack.
- KYA requirements confirmed during program design
- KYC for individual verification
- KYB for business verification
- KYT and ongoing transaction screening
FinCEN MSB, FINTRAC MSB and Hong Kong TCSP disclosures apply to the entities and scopes listed on our Licenses page. MSB registration and TCSP licensing are not a bank charter or scheme Principal membership.
See complianceMore than the card.
Connect cards, accounts, wallets and acquiring as your business grows.
What DogPay CaaS is
DogPay Card as a Service gives fintechs, marketplaces and Web3 businesses the APIs to build branded virtual and physical card programs. DogPay orchestrates the integration with issuing partners; it is not presented as a bank or a scheme Principal Issuer. Combine cards with the account, wallet or acquiring products that fit your business.
- White-label virtual and physical cards
- Credit and prepaid program options
- API-based issuance and card controls
- Crypto funding and connected financial services
Who handles what?
Agree the operating model before launch. The program agreement determines the final division of responsibilities.
| Your business | DogPay and issuing partners |
|---|---|
| Brand and card artwork | Card program integration and design review coordination |
| Your customer journey and use-case rules | Issuance orchestration and documented card controls |
| Commercial pricing within agreed terms | Program pricing and eligibility requirements |
| Required customer data and your compliance obligations | KY* workflows and partner risk processing as agreed |
| Your application, policies and reconciliation logic | Wallet provisioning support, funding and transaction interfaces by program |
Cards, accounts, wallets and acquiring — connected
Use DogPay’s broader platform when your card program also needs virtual accounts, wallets or merchant acquiring. Each product has its own onboarding, API scope and availability. A shared platform does not mean that every service uses the same credentials, balance or settlement route. Review the relevant documentation and confirm how the services connect.
- CaaS for card program orchestration
- BaaS for account integration
- Wallet and payment services for supported flows
Who is it for?
Explore programs for crypto spending, cross-border merchants and platforms serving customers in Nigeria and Latin America. These are use-case and market discussions, not claims of local issuing licences or universal cardholder eligibility. Confirm the permitted customer base, funding route and issuer requirements before building the customer journey.
- Fintechs launching a branded card experience
- Web3 platforms connecting crypto funding to card spend
- Cross-border merchants and marketplaces
- Nigeria and Latin America use cases, subject to eligibility
Your card program, from fit to launch.
Scope your program
Confirm customer markets, credit or prepaid, funding routes and required controls.
Agree responsibilities
Complete eligibility and KY* requirements, partner checks and commercial terms.
Integrate and test
Use the sandbox and document card lifecycle, funding, authorization and event handling.
Prepare for launch
Complete required approvals, operational checks and production access. Timing depends on scope and review.
Questions before you build
Can cards support Apple Pay and Google Pay?
Yes, on eligible card programs. Availability depends on the issuer, card type, region and wallet provisioning requirements. Confirm the selected program before promising wallet support to users.
Can we customize the card design?
Yes. Card face customization is available, subject to the selected program’s production and network design review. The on-page preview is illustrative and does not submit a production order.
What does 50+ API clients mean?
DogPay confirms 50+ API clients integrated as of October 1, 2026. This is an integration-client count, not a count of cards issued, cardholders or active monthly users.
What do KYA, KYC, KYB and KYT cover?
Program workflows include KYA requirements, individual KYC, business KYB and transaction KYT controls. The KYA scope, checks, screening responsibilities and ongoing monitoring are defined at onboarding for the selected program.
Is DogPay a scheme Principal Issuer or a bank?
DogPay provides program integration and orchestration through BIN sponsor relationships and partner issuers. This page does not claim that DogPay is a Visa or Mastercard Principal Issuer or a bank. MSB and TCSP disclosures are separate from those statuses.
Do you offer credit or only prepaid?
Both credit and prepaid program options are available. Eligibility, credit terms, funding arrangements and supported features depend on the selected issuing program.
Which issuing regions are available?
Program corridors include Hong Kong, Singapore, the UK and the US. The issuer, applicant and cardholder requirements must be confirmed for your program. This is not a statement of local issuing permission in Nigeria or Latin America.
Does every card program use Flagright?
No. Selected card programs use Flagright as a risk processor; other partners may use alternate stacks depending on the issuing corridor. Flagright is not described here as an issuer, BIN holder or scheme member.
How does CaaS connect with BaaS and wallets?
CaaS can be planned alongside DogPay’s account, wallet and acquiring products. Confirm separate product access, APIs, balances and funding routes rather than assuming one integration automatically activates every service.
How long does integration take?
Timing depends on the integration scope, issuing arrangement, eligibility review and production approvals. Technical sandbox work and a fully approved program launch are different milestones; request a project-specific plan.
Are physical card delivery times guaranteed?
Production and logistics depend on the program and destination. Confirm delivery options and timing with the team before committing to a launch date.
Can a card authorization callback wait for user confirmation?
Obtain required user approval before submitting the transaction. The CaaS authorization documentation currently specifies a 500ms response deadline including network latency, subject to card capabilities. Confirm program access and timing with your account manager.
Build the right card program before you build the integration.
Discuss your markets, funding model and customer experience. We will help confirm the available issuing arrangement, documentation and next steps.