Security and Compliance
Paytrim's recommendations to merchants and partners that integrate with or use Paytrim's services, with a focus on online payments: which integration to choose, what it means for PCI DSS, and how to secure the parts that remain your responsibility.
About this guide
If cardholders enter card details only on Paytrim's Hosted Payment Page, your PCI DSS scope is small. Most merchants can then validate with SAQ A. Every integration choice that moves card data or checkout scripts closer to your own systems increases what you must protect and prove.
This guide is for:
- Merchants that accept online card payments through Paytrim.
- Partners (integrators, platforms and ISVs) that build, host or operate checkouts for Paytrim merchants, or that integrate with the Paytrim API.
It explains which integration to choose, what each choice means for PCI DSS v4.0.1, and how to secure the parts that remain your responsibility. It supports, but does not replace, your agreement with Paytrim: the General Terms for E-commerce Card Acquiring, the Instructions for Merchants – E-commerce and, for partners, the partner agreement and its appendices. Where this guide and those documents differ, the agreements prevail.
Integration options and PCI DSS scope
Choose the Hosted Payment Page with full-page redirect unless you have a specific reason not to. It is the only way to take card details where neither the card data nor the scripts on your checkout are in scope for the PCI DSS script requirements. Apple Pay and Google Pay host-to-host (profile E2) can be added next to it without changing your SAQ.
| Profile | Integration | Card data in your systems | Typical SAQ | Script requirements (6.4.3, 11.6.1) |
|---|---|---|---|---|
| E1 | Hosted Payment Page opened by full-page redirect (order_url, or the
transaction's payment_url when the customer selects the payment method in
your checkout), payment links, recurring and one-click payments with
vault_token and without cvc |
None. Only tokens and truncated card numbers | SAQ A | Do not apply |
| E1-iframe | As E1, but your checkout also embeds card fields of another payment provider (iframe or script) | None | SAQ A | Apply to the page that embeds the other provider's fields (see below) |
| E2 | Apple Pay or Google Pay host-to-host with encrypted payload. Paytrim holds the decryption
keys. Google Pay only with the CRYPTOGRAM_3DS authentication method |
Encrypted payload you cannot decrypt | SAQ A | Do not apply to the wallet button |
Profile E2 is switched off by default; Paytrim enables it for a project on request. The SAQ type that applies to you is set by Paytrim; the table shows the usual outcome.
Paytrim does not offer integrations where card data or cvc is entered on, or passes through,
your own pages or servers: no card form of your own, no cvc through the API, no wallet
payloads decrypted with your own keys, and no AFT to a card account.
Using a hosted page does not take your website out of scope altogether. Paytrim's payment page cannot be embedded in your website; it is always opened by full-page redirect. The page that redirects to Paytrim's page can be manipulated to send cardholders to a fake payment page. That is why SAQ A still covers your website, and why the rest of this guide matters even for profile E1.
Hosted Payment Page via redirect
With full-page redirect, the cardholder leaves your site and enters card details on Paytrim's page. Paytrim manages and monitors the scripts on that page. Your responsibility is to make sure the redirect cannot be tampered with.
How the flow works
- Your server creates an order through the Merchant API, using your API credentials.
- Paytrim returns an
order_urlfor the order. If you send atransactionslist with the payment method the customer selected in your checkout, use the transaction'spayment_urlinstead of theorder_url. - Your checkout sends the browser to that URL with a full-page navigation, not in a frame or pop-up.
- The cardholder pays and completes 3-D Secure on Paytrim's page.
- Paytrim sends the cardholder back to your return URL. Your server confirms the result through the Merchant API before you fulfil the order.
Requirements
- Create the payment URL on your server. Never build it in the browser or take it from
a query string, a cookie or user input. Before redirecting, check that the URL begins with
https://api.pay.paytrim.com/pay/. This stops an attacker from swapping the link for a fake payment page. - Serve your whole site over HTTPS with TLS 1.2 or newer, and set
Strict-Transport-Security. - Never trust the return URL alone. Query parameters on the return can be forged. Check the order status server-to-server before you ship goods or mark an order as paid.
- Keep the checkout step clean. Do not load analytics, session recording, chat or A/B testing scripts on the page that starts the redirect.
- Patch your platform. Keep the e-commerce platform, themes and plug-ins up to date (PCI DSS 6.3.3) and remove those you do not use.
- Protect administration. Use unique accounts and multi-factor authentication for everyone who can change your website or checkout.
The PCI DSS script requirements 6.4.3 and 11.6.1 do not apply to a page that only redirects the full page. The page is still part of your SAQ A scope, because a compromised site can redirect cardholders to a fake payment page.
Another provider's embedded card fields and script security
If your checkout also embeds card fields or a payment page of another payment provider, in an iframe or by script, you must confirm that your page cannot be used for a script attack. This is an eligibility criterion for SAQ A since PCI DSS v4.0.1 and the January 2025 revision of SAQ A.
You can meet the criterion in one of two ways: apply the techniques in PCI DSS 6.4.3 and 11.6.1 to the page that embeds the other provider's fields (see the table below), or get a written confirmation from that provider that its solution, when implemented according to its instructions, protects your page against script attacks (PCI SSC FAQ 1588).
| Requirement | What PCI DSS asks | What to do on the page that embeds the other provider's fields |
|---|---|---|
| 6.4.3 | Every script on the payment page is authorised, its integrity is assured, and there is an inventory with a written justification for each script | Keep a list of every script: its source, owner and purpose. Approve new scripts before release. Load only scripts you need, and pin them with Subresource Integrity (SRI) or a strict Content Security Policy (CSP) |
| 11.6.1 | A change- and tamper-detection mechanism alerts on unauthorised changes to security-relevant HTTP headers and to the script contents of the payment page, as received by the browser | Monitor the page as the cardholder sees it, at least weekly or at the frequency in your risk analysis. Use CSP reporting or a commercial script-monitoring service, and act on the alerts |
Practical advice
- Put the embedded fields on a dedicated page with as few scripts as possible. Fewer scripts mean a shorter inventory and fewer alerts.
- Do not let scripts create or move the iframe unless you control those scripts. If a third-party tag builds the payment frame, that tag is part of your scope.
- Use the Content Security Policy below. CSP with a strict
script-srcandframe-srccovers much of 6.4.3, and CSP violation reports can feed your 11.6.1 monitoring. - Expect to buy a monitoring service if your checkout uses many third-party tags. Manual review rarely keeps up.
If this is more than you want to maintain, send cardholders to the other provider by full-page redirect as well. That removes the script requirements altogether.
Content Security Policy and Subresource Integrity
A Content Security Policy (CSP) tells the browser which sources your checkout may load scripts and frames
from. It is the most effective single control against script attacks on your page. Start in report-only
mode (Content-Security-Policy-Report-Only), fix what it reports, then enforce it.
Recommended policy for your checkout:
Content-Security-Policy:
default-src 'self';
script-src 'self' 'nonce-{random-per-response}' 'strict-dynamic';
connect-src 'self';
img-src 'self' data:;
style-src 'self';
object-src 'none';
base-uri 'none';
form-action 'self';
frame-ancestors 'self';
upgrade-insecure-requests;
report-to csp-endpoint;
Notes on the directives
frame-srcis not needed for Paytrim, since Paytrim's payment page is opened by full-page redirect. If your checkout embeds another provider's card fields, allow only that provider's domain inframe-src.script-srcwith a nonce lets only scripts you have tagged run. Generate a new random nonce for every response. Avoid'unsafe-inline'and'unsafe-eval'.frame-ancestors 'self'stops other sites from framing your checkout (clickjacking).report-tosends violations to an endpoint you monitor. Combined with a review routine, this supports PCI DSS 11.6.1. Add aReporting-Endpointsheader that definescsp-endpoint.- Apple Pay and Google Pay on your own page (profile E2) need their script and frame
sources added, for example
https://applepay.cdn-apple.comandhttps://pay.google.com. Check the wallet providers' current documentation.
With full-page redirect, the policy is not required for PCI DSS, but it protects the page that starts the redirect.
Subresource Integrity (SRI)
If you load a script from a third-party server, add an integrity attribute with its hash, for
example:
<script src="https://cdn.example.com/lib.js"
integrity="sha384-…"
crossorigin="anonymous"></script>
The browser then refuses the script if its contents change. SRI works only for files that do not change without a new version; it cannot be used for tag managers or scripts that update themselves.
Other security headers
Set these on checkout pages: Strict-Transport-Security,
X-Content-Type-Options: nosniff and
Referrer-Policy: strict-origin-when-cross-origin. PCI DSS 11.6.1 asks you to detect
unauthorised changes to these headers as well.
API credentials
Treat your Paytrim credentials like a bank password. This applies to the Merchant API key for online payments and to the client secret you use for the Paytrim API.
A Merchant API key gives full access to its project. With it, someone can refund payments, charge saved cards, read orders with customer details and, where enabled, send payouts to cards.
How Paytrim issues Merchant API keys
- One set of API credentials per project.
- Test credentials first. Production credentials only after Paytrim has verified your integration.
- Keys are delivered through a secure channel, never in plain-text e-mail. When a partner installs the integration, Paytrim delivers the key to the partner only after the merchant has authorised it in writing.
- Only Paytrim can revoke and reissue a key. Paytrim may do so without notice if it suspects misuse.
Your requirements
- Call the API only from your server. Never put an API key or client secret in a browser, a mobile app or any code that runs on the customer's device.
- Store credentials in a secrets manager (for example Azure Key Vault, AWS Secrets Manager or HashiCorp Vault). Never in source code, configuration files in a repository, e-mail, chat, tickets or shared documents.
- Limit access to named people who need it, protected by multi-factor authentication. Keep a record of who has had access.
- Use TLS 1.2 or newer for every API call and validate Paytrim's certificate. Do not disable certificate checks, not even in test.
- Do not log secrets or card data. Mask API keys, client secrets and access tokens in
logs and error reports. Never log full card numbers or
cvc. - Verify, don't trust. Before you fulfil an order, read its status from the API. Do not rely only on the return URL or a message that arrives at your endpoint.
- Watch your own activity. Review refunds and unusual orders regularly. Unexpected refunds are a common sign of a stolen key.
- Tell Paytrim within 24 hours if you suspect that a key or secret has been exposed. Tell Paytrim without undue delay when you change partner or when someone with access leaves. Paytrim will issue new credentials.
Ask only for the features you use
One-click payments, which the cardholder starts and authenticates with 3-D Secure, and recurring and other merchant-initiated payments are off by default. Paytrim enables them per merchant on request and after approval. Refunds through the API are switched off at onboarding and enabled on request, and host-to-host wallets are enabled per project on request. AFT to a card account is not available. Other AFT and OCT are not available without a separate agreement. Each feature widens what a stolen key can do.
cvc with one-click, recurring or other stored-card payments, even
where the gateway documentation shows the field. Sending cvc is not permitted.
Platforms and partners
If you host, operate or hold API keys for a merchant's checkout, you are a third-party service provider (TPSP) under PCI DSS. This applies even when card details are only entered on Paytrim's page. A platform that redirects to Paytrim's page controls the step where cardholders can be sent to a fake page.
Paytrim classifies partners in the partner agreement:
| Role | What you do | TPSP for the merchant? |
|---|---|---|
| Integrator | Builds or configures the checkout and hands it over. No ongoing access to the website or API keys | No, once handed over |
| Managing Integrator | Hosts, operates or maintains the merchant's website, has admin access, or holds its API keys | Yes |
| Platform Partner | Runs a shared platform where several merchants' checkouts run | Yes, for every merchant on the platform |
What this means for you as Managing Integrator or Platform Partner
- Your merchants must manage you as a service provider (PCI DSS 12.8). Expect them to ask for your PCI DSS status.
- Give each merchant a responsibility split (PCI DSS 12.9.2): which requirements you manage, which they manage, and which are shared. You can build on Paytrim's PCI DSS Responsibility Matrix, which Paytrim sends you on request.
- Apply this guide to your platform. Use full-page redirect to Paytrim, a strict CSP, no third-party tags on the checkout step, patching, MFA for all admin access and API keys in a secrets manager.
- Help merchants with their SAQ. The SAQ is the merchant's own and signed by the merchant. Your help does not move their obligations to you.
- Notify Paytrim before you change the platform, hosting or checkout flow in a way that affects payments.
Approved platforms
Paytrim approves Platform Partners' platforms against its Technical Requirements for Platform Partners, which Paytrim provides on request. An approved platform signs an annual self-declaration against those requirements and sends Paytrim the results of its quarterly external scans for the last four quarters every year. Paytrim checks approved platforms' checkout pages itself. In some cases, for example above a volume threshold, after a security incident, or if the checkout embeds another provider's card fields, Paytrim requires an Attestation of Compliance for Service Providers in addition.
Merchants on an approved platform can use the platform's self-declaration and Paytrim's approval when they check their service providers (PCI DSS 12.8.4). A Managing Integrator cannot be approved: merchants whose website it manages validate with their own SAQ and AOC, and the Managing Integrator supports them with the information in 12.8.4, 12.8.5 and 12.9.2.
Validating your compliance
What you submit depends on your integration profile and your annual card transaction volume.
| Your situation | What you submit | When |
|---|---|---|
| Profile E1 or E2 through an approved platform, Level 4 (fewer than 20,000 e-commerce transactions per card brand per year) | Confirmation in your agreement that you meet the SAQ A criteria. The platform's quarterly scans by an Approved Scanning Vendor (ASV) cover your checkout (PCI DSS 11.3.2). Scan any other website you run yourself if it links to the checkout | At signing, and whenever your integration changes |
| Profile E1, E1-iframe or E2 with your own integration, or on a platform that Paytrim has not approved, Level 4 | SAQ A and AOC, plus quarterly external scans of your website by an ASV (PCI DSS 11.3.2) | Within 90 days of your first e-commerce transaction, then every year |
| Profile E1, E1-iframe or E2, Level 3 (20,000 to 1 million e-commerce transactions per card brand per year) | SAQ A and AOC, plus quarterly external scans of your website by an ASV (PCI DSS 11.3.2) | Every year |
Levels 1 and 2 (over 1 million transactions per card brand per year) follow the card schemes' rules and are agreed with Paytrim case by case.
What Paytrim provides to you
- The PCI DSS Responsibility Matrix for your integration profile, on request.
- Evidence of the PCI DSS compliance of the Paytrim Payment Solution, on request.
- Answers to which SAQ applies to you.
Paytrim reviews a sample of merchant checkouts each quarter. The review covers whether the checkout uses full-page redirect to Paytrim, the scripts on the page and the CSP.
Suspected compromise
Tell Paytrim without undue delay, and within 24 hours at the latest, if you suspect that your checkout, payment flow, API key or client secret has been compromised. Report suspicions too; you do not need proof.
Report, for example
- an unknown or changed script on a checkout page, or a CSP or monitoring alert you cannot explain,
- a redirect or iframe that points somewhere other than Paytrim,
- customers reporting a payment page that looked different, or fraud shortly after buying from you,
- refunds or orders you did not make,
- an API key or secret found in a repository, log, ticket or e-mail, or held by someone who has left.
What to do
- Contact Paytrim at itoperations@paytrim.com.
- Preserve evidence. Keep logs, the affected pages and scripts, and a copy of the changed files. Do not wipe or rebuild servers before you have agreed this with Paytrim.
- Contain the damage. Remove the malicious code or switch to full-page redirect. Paytrim can revoke your credentials and suspend payments while the incident is investigated.
- Cooperate with Paytrim, the card schemes and any forensic investigator (PFI) they appoint.
Partners that serve several merchants also give Paytrim a list of the merchants and projects affected.
Checklist
Go through this list before you go live, and again after any change to your checkout.
- Card details are entered only on Paytrim's page, opened by full-page redirect
- The payment URL is created on your server, never in the browser
- The order status is checked through the API before fulfilment
- The whole site uses HTTPS with TLS 1.2 or newer and HSTS
- No analytics, session recording, chat or A/B scripts on the checkout step
- Another provider's embedded card fields only: a script inventory with a justification per script (6.4.3)
- Another provider's embedded card fields only: weekly change and tamper detection of scripts and headers (11.6.1)
- A Content Security Policy is enforced and its reports are monitored
- Platform, themes and plug-ins are patched; unused ones are removed
- Quarterly external vulnerability scans of your website by an ASV pass (11.3.2)
- MFA for everyone with admin access to the site or the merchant portal
- API keys and client secrets are in a secrets manager, used only from your server, and masked in logs
- You know who to contact at Paytrim if something looks wrong
- Partners: merchants have received your responsibility split (12.9.2)
Sources
- PCI SSC Document Library – PCI DSS v4.0.1 (requirements 6.4.3, 11.6.1, 12.8 and 12.9) and SAQ A
- PCI SSC FAQ 1588 – SAQ A eligibility criteria for scripts
- MDN – Content Security Policy
- MDN – Subresource Integrity