Introduction
Welcome to ePay, your comprehensive Payment Service Provider (PSP) solution designed to simplify and secure digital transactions for businesses of all sizes.
This documentation will guide you through integrating ePay into your platform, enabling you to accept payments efficiently and reliably.
Why Choose ePay?
Comprehensive Features
- One-time payments (CIT)
- Storing payment details for subsequent transactions (CIT)
- Recurring billing and subscriptions (MIT)
- Refunds, voids, and payouts
- Advanced risk mitigation capabilities to integrate custom anti-fraud workflows
- Detailed transaction logs for enhanced transparency
- Card tokenization to reduce churn by updating expired cards automatically.
- Hosted fields to embed the payment flow directly into your page with your branding.
- A pre-built payment window for quick startup and low integration overhead.
- Dynamic Surcharging: Implement advanced fee calculation rules, including recursive fees, VAT-inclusive/exclusive configurations, and percentage-based surcharges. Rules can adjust based on card type, issuer region (domestic, EU/EEA, or non-EU/EEA), and corporate vs. consumer cards.
Begin Your Integration
Follow these steps to integrate ePay into your platform and start accepting payments.
Familiar yourself with sessions, transactions, and subscription workflows.
Create an ePay account and obtain your API keys from the ePay backoffice.
Select which product you want to use and follow the guide for embedding it.
Use the provided Test Cards to validate your setup and handle edge cases.
Once testing is complete, switch to production mode and start processing real transactions.
Looking for clear instructions and API references to implement ePay into their applications.
Seeking to understand the capabilities and benefits of using ePay as a payment solution.
Detailed technical documentation of ePay endpoints, available in the API section.
Explore all supported payment methods and their requirements in the Payment Methods section.
Stay updated on new features and changes in the Changelog section.