Clear authorisation
Present frequency, amount rules and merchant identity before consent.
Recurring authorisation
eMandate experiences with consent at the centre.
Build recurring collection journeys around explicit authorisation, mandate state, debit notification and controlled retries.
PayDrion
Consent record
Consent-first collection
Illustrative product operating view
What the customer authorised, and what happened next.
PayDrion operating record
Consent record
Consent captured
1
Merchant
2
Amount rule
3
Frequency
4
Validity
Evidence boundary
Consent-first collection
Consent captured
Mandate active
Retry governed
eMandate lifecycle
Mandate terms should remain visible after authorisation.
PayDrion keeps authorisation evidence, status, debit history, notifications and controlled retry decisions together.
Mandate vault view
Keep mandate references, status and linked debit history searchable.
Policy-based retries
Retry only within applicable rules and merchant-defined collection policy.
eMandate lifecycle
Recurring authorisationDedicated product layer · shared PayDrion evidence model
Mandate terms should remain visible after authorisation.
PayDrion keeps authorisation evidence, status, debit history, notifications and controlled retry decisions together.
Recurring authorisationDedicated product layer · shared PayDrion evidence model
PayDrion product architecture
Consent-first collection
Merchant
Present frequency, amount rules and merchant identity before consent.
Consent captured
Amount rule
Keep mandate references, status and linked debit history searchable.
Mandate active
Frequency
Retry only within applicable rules and merchant-defined collection policy.
Retry governed
Validity
Present frequency, amount rules and merchant identity before consent.
Consent captured
PayDrion evidence lineRequest · decision · partner reference · signed event · operator action
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
SaaS billing
02
EMI collection
03
Insurance premiums
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.