1. 3-D Secure / Strong Customer Authentication (SCA)
What it is: An extra layer of security required for many online payments in Europe (PSD2 regulation).
How it works: During checkout, the customer may be asked to confirm the payment with their bank app, SMS code, fingerprint, or face recognition.
Why it matters:
Protects against fraud
Shifts liability from you (the merchant) to the bank when the authentication succeeds
Required for compliance in the EU
When you need it: Always enabled by default; customers will only see it when their bank requires extra verification.
2. Tokenization / Card-on-File / Recurring Payments
What it is: A secure way to store customer card details as a “token” for future payments.
How it works: Instead of saving the card number, Paynt generates a unique token that can be reused for subscriptions, one-click payments, or repeat customers.
Why it matters:
Enables subscription models (weekly, monthly, yearly billing)
Makes checkout faster for returning customers (no need to re-enter card details)
Tokens are secure and PCI compliant
When you need it: If you offer subscriptions, memberships, or want to improve repeat customer experience.
3. Webhooks & Payment Notifications
What it is: Real-time notifications from Paynt to your system when a payment event happens.
How it works: Each time a payment is approved, declined, or refunded, Paynt can “push” this information automatically to your system.
Why it matters:
Keep your shop backend and inventory updated automatically
No need to manually refresh or check the back office
Essential for handling asynchronous payments (where confirmation may come a few seconds later)
When you need it: If you want your shop to update orders, invoices, or services instantly once payment status changes.
4. SDK or Custom UI Integration (Beyond the Widget)
What it is: Instead of using the hosted widget, your development team can build a fully custom checkout using Paynt’s SDK or APIs.
How it works: Your shop collects customer details in a secure way and communicates directly with Paynt’s platform through the SDK.
Why it matters:
Offers complete design control over the checkout experience
Useful for mobile apps or highly customized websites
Gives flexibility for advanced business models
When you need it: If you want to fully control the look and flow of your checkout or if you operate a mobile app.
Next Steps
Decide which of these features fits your business model.
Share the choice with your technical team for setup.
For implementation details, see our Developer Documentation or contact our Support Team.