Transport
Use HTTPS for merchant pages, backend requests, return URLs, and callbacks.
Security approach
Protect the payment decision
A secure integration limits credential exposure, verifies payment status, validates events, records references, and makes unusual states visible.
Apply for merchant accessControl layers
Security belongs across the route
Commercial noteThis page describes an intended security approach. It does not claim a certification, licence, audit result, or scheme membership.
Credentials
Keep secret values on the server, use separate test and production access, and rotate when required.
Verification
Confirm the authoritative payment status before fulfilment, access, or accounting updates.
Events
Validate incoming notifications, handle duplicates safely, and preserve event references.
Operations
Restrict merchant access, review unusual activity, and keep refund actions accountable.
Merchant responsibilities
The gateway cannot secure a broken order flow
The merchant website, application, staff access, and fulfilment logic remain part of the payment security boundary.
Website readiness
Use current software, secure administration, accurate product information, and visible customer policies.
Server logic
Do not trust query parameters, browser messages, or customer screenshots as proof of payment.
Access control
Give staff the minimum access required and remove accounts that are no longer needed.
Incident path
Know how to pause fulfilment, preserve evidence, and contact the payment team when a transaction looks wrong.