Payment gateway integration: follow the money and the record
Current service configuration: Wayl enabled, live and healthy; PayPal, Stripe and PayTabs disabled and unconfigured. This concerns Datrylo subscriptions. A payment connection for your own ERP customers is a separate integration. No payment is made by this page or this review.
What is available for this connection
| Current status | Wayl live for Datrylo subscriptions; other providers disabled |
|---|---|
| Operation | Datrylo subscription checkout through Wayl in IQD |
| Implementation | Current service configuration: Wayl enabled, live and healthy; PayPal, Stripe and PayTabs disabled and unconfigured. This concerns Datrylo subscriptions. A payment connection for your own ERP customers is a separate integration. No payment is made by this page or this review. |
Before enabling a provider
Confirm the legal seller, supported markets, charge and settlement currencies, taxes, refund capability and customer disclosure. Store credentials securely and version them. The browser should never supply the final amount or decide market eligibility. The Manager must create an authoritative attempt and bind provider callbacks to its reference, amount, currency and customer.
Handle uncertain outcomes
A redirect is not payment proof. Timeouts, repeated callbacks and delayed provider status need idempotent handling and reconciliation. Treat each external connection as a scoped integration: confirm the provider, supported data, permissions, fees and error handling before relying on it.
Test refunds and history
Check partial refunds, duplicate events, credits and regeneration of historic documents after rates or prices change. Record the original conversion context. Discuss a payment requirement.
Ready for your
next big move?
See what a more connected business could look like. Start with a conversation about yours.