Sender lifecycle
Maintain required identity, limit and transaction context for the programme.
Domestic remittance
DMT APIs for approved remittance programmes.
Support eligible domestic money-transfer flows through regulated partners with sender onboarding, beneficiary controls and transaction limits.
PayDrion
Remittance workflow
Controlled remittance
Illustrative product operating view
Sender onboarding to beneficiary transfer under programme limits.
Sender
Sender active
Beneficiary
Beneficiary ready
Limit
Transfer tracked
4
Transfer
Sender active
Current operating signal
Controlled remittance
Each state remains linked to the originating PayDrion record.
Sender active
Beneficiary ready
Transfer tracked
DMT API
A remittance request begins with sender and programme eligibility.
PayDrion applies partner and risk limits, maintains beneficiary context and maps each transfer outcome to its remittance record.
Beneficiary book
Add and verify recipients before initiating transfers.
Limit enforcement
Apply partner, regulatory and risk limits at request time.
DMT API
Domestic remittanceDedicated product layer · shared PayDrion evidence model
A remittance request begins with sender and programme eligibility.
PayDrion applies partner and risk limits, maintains beneficiary context and maps each transfer outcome to its remittance record.
Domestic remittanceDedicated product layer · shared PayDrion evidence model
PayDrion product architecture
Controlled remittance
Sender
Maintain required identity, limit and transaction context for the programme.
Sender active
Beneficiary
Add and verify recipients before initiating transfers.
Beneficiary ready
Limit
Apply partner, regulatory and risk limits at request time.
Transfer tracked
Transfer
Maintain required identity, limit and transaction context for the programme.
Sender active
PayDrion evidence lineRequest · decision · partner reference · signed event · operator action
Programme boundary
API availability does not equal permission to operate the underlying regulated service.
Activation requires an eligible business model, authorised partner structure, documented operating responsibilities and applicable customer-protection controls.
Where it fits
Designed around the job the money movement must complete.
Configuration follows the real transaction purpose, customer experience and operating responsibility—not a one-size-fits-all product label.
01
Assisted remittance
02
Retailer networks
03
Partner-led DMT
Questions
Practical answers before implementation.
Commercial and technical details are confirmed for the specific entity, use case and approved programme.
How does implementation begin?+
PayDrion first maps your business model, transaction flow, expected volumes, risk profile and required payment rails. An implementation plan and test credentials follow successful onboarding.
Can this be enabled for every business?+
Availability, limits, pricing and settlement timelines depend on onboarding, use case, bank or network partner approval, and applicable regulation.
How are transaction states confirmed?+
Use the synchronous API response for immediate context, then rely on signed webhooks and server-side status verification as the operational source of truth.