Shared payment responsibility
Security is an operating system, not a badge.
The final control set depends on the selected payment route and merchant architecture. This page explains the approach without claiming certifications or partner controls that have not been independently established for this service.
Minimise exposure
Keep sensitive payment data out of unnecessary systems.
The preferred integration boundary should reduce the merchant’s direct handling of payment credentials where the approved route allows. Sensitive fields should be collected by the appropriate payment environment, transmitted using current encryption, and stored only where a documented requirement and control set exist.
Card security codes, complete card numbers, passwords, one-time codes, and secret API keys should not be placed in support messages or attachments.
Access
Give each person and system only the access it needs.
- Separate user accounts instead of shared credentials.
- Use strong authentication and additional verification where available.
- Restrict production keys to server-side systems and approved personnel.
- Review access when roles change and remove it when no longer needed.
- Separate test and production configuration and credentials.
Detection and evidence
Make important payment events reviewable.
Useful records can include authentication events, credential changes, API access, payment-state changes, refunds, export activity, webhook delivery, and administrative actions where the selected platform exposes them. Logs should be protected from casual alteration and retained according to the approved operating and legal requirements.
Merchant-side monitoring still matters
Alert on unusual checkout failures, repeated signature errors, spikes in refunds, unexpected credential use, and gaps between orders, gateway states, and settlement records.
Merchant responsibilities
The gateway cannot secure an unsafe store.
Merchants remain responsible for the security of their website, application, staff access, product fulfilment, customer support, privacy notices, and the systems that create orders or decide when to deliver value.
- Patch ecommerce platforms, plugins, libraries, and server software.
- Protect administrator accounts and remove unused integrations.
- Validate all prices, order references, and fulfilment rules on the server.
- Keep secrets out of source repositories, client-side code, and screenshots.
- Maintain an incident path that connects engineering, operations, and support.
Report a concern
Route security and compliance questions directly.
Use the compliance inbox for suspected vulnerabilities, policy concerns, legal requests, or sensitive security coordination. Provide the affected URL or component, a concise description, safe reproduction steps, and potential impact. Do not access data that is not yours or disrupt the service to prove a point.