PAYMENTS · MERCHANT, COMMERCE AND CROSS-BORDER
DiPay.Ai
Payment technology that organizes the handoffs, not the licence.
Payment technology in development for merchants, digital-commerce platforms and financial institutions coordinating payment instructions across separate providers and settlement systems. Regulated payment services remain with licensed providers; no live payment service is represented.
AT A GLANCE
A payment is a chain of handoffs.
What a customer experiences as one tap is, operationally, several steps: checkout, authorization, acquiring, currency handling, settlement and reconciliation. Each step may be run by a different provider, and the merchant is left holding the task of making the records agree afterwards.
DiPay.Ai is designed as the connective layer across those steps. A commerce event becomes a structured payment instruction; the instruction is routed to an authorized provider; the status, reference and settlement information comes back into one record the merchant and its finance team can work from. For cross-border flows, the design documents the provider, currency and settlement handoffs a corridor would require.
DAC develops the workflow and the connectivity. It does not hold funds, issue accounts or process payments. Licensed payment providers deliver payment accounts, processing, money movement and other regulated services under their own permissions and terms. DiPay.Ai is in development, and no live payment service or coverage is represented.
DESIGNED TO WORK
How the workflow is meant to run.
A sequence of designed handoffs, not a description of live processing. Every stage names the provider or institution that would have to act.
WHO IT IS FOR
The teams this pillar is built around.
Merchants and marketplaces
Businesses selling across several channels that need one view of payment instructions, provider handoffs and settlement records.
Commerce and booking platforms
Travel, booking and marketplace teams connecting a checkout workflow to a payment provider without owning the regulated payment layer.
Payment providers and banks
Licensed institutions exploring how a commerce workflow could deliver cleaner instructions and reconciliation data to their own systems.
WHERE THE DESIGN APPLIES
The workflows this pillar is meant to support.
A customer payment can pass through separate checkout, acquiring, wallet and settlement systems, while merchants still need clear records of each handoff.
What DAC would doDiPay.Ai is in development as payment technology and connectivity. DAC’s proposed role is to organize the digital workflow; licensed payment providers would deliver payment accounts, processing, money movement and other regulated services.
Merchant payment instructions
Map how a commerce platform could connect checkout events with payment-provider instructions and transaction records.
Booking and commerce payments
Explore how booking or marketplace workflows could pass payment details to an authorized provider.
Cross-border payment coordination
Document provider, currency and settlement handoffs for a future cross-border workflow, subject to licensed partners and market requirements.
PLAIN ANSWERS
Questions institutions ask first.
Can I accept payments through DiPay.Ai today?
No. DiPay.Ai is in development and no live payment, processing, coverage or settlement service is represented. Payment accounts and money movement must come from a licensed provider.
Is DiPay.Ai a wallet or a payment institution?
Neither. It is a proposed technology and connectivity layer. DAC is not represented as a bank or a regulated payment institution, and would not hold customer funds.
Who would process the payment?
An appropriately licensed payment provider. DAC’s proposed role is to organize the digital workflow and the handoffs; acquiring, accounts, money movement and settlement are delivered under the provider’s own permissions.
Does it promise lower fees or faster settlement?
No. The design describes how instructions and records could connect. No processing time, fee saving, comparative benefit or live settlement capability is represented.
CONNECTED SYSTEM
What this pillar touches in the ecosystem.
- RWAUSD.AiProgrammable settlement architecture that a payment instruction could hand off into.
- DigitalBooking.AiBooking and travel-commerce workflows that could pass payment details to a provider.
- Chain.RWA.winDigital records and settlement workflow design beneath the payment layer.
- DigiLending.AiCredit and deferred-payment workflows that settle through the same rails.
STATUS, CONTROLS AND CONDITIONS
Technology and connectivity, not a payment licence.
DiPay.Ai is a DAC-developed payment concept in development. Money transmission and payment services require appropriately licensed providers, and DAC is not represented as a bank or a regulated payment institution. Payment accounts, processing, money movement and settlement would be delivered by authorized providers under confirmed arrangements.
No live service. Coverage, processing capability and settlement timing depend on licensed partners and are not represented on this page.
- Payment workflow and provider connectivity
- Merchant, commerce and cross-border payments
Payment technology and connectivity. Digital Assets Capital is not represented as a bank or a regulated payment institution.
- DEPENDENCY
- Payment rails, acquiring and wallet infrastructure through partners
- AVAILABILITY
- Subject to jurisdiction, eligibility and applicable requirements
- Merchant Verification
- Payment Controls
- Transaction Monitoring
- Settlement Reporting
Subject to jurisdiction, eligibility and applicable requirements
PAYMENTS · MERCHANT, COMMERCE AND CROSS-BORDER
Mapping a payment workflow?
Bring the corridor, the commerce flow and the providers already involved. The conversation is about the handoffs and the record they leave behind.