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:

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.

Shared responsibility Paytrim operates the payment page, card vault, tokenisation, 3-D Secure and authorisation. You are responsible for your website, the page that sends the cardholder to Paytrim, your servers and your API credentials. The full split per PCI DSS requirement is in the PCI DSS Responsibility Matrix, which Paytrim sends to merchants and partners on request.

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

  1. Your server creates an order through the Merchant API, using your API credentials.
  2. Paytrim returns an order_url for the order. If you send a transactions list with the payment method the customer selected in your checkout, use the transaction's payment_url instead of the order_url.
  3. Your checkout sends the browser to that URL with a full-page navigation, not in a frame or pop-up.
  4. The cardholder pays and completes 3-D Secure on Paytrim's page.
  5. Paytrim sends the cardholder back to your return URL. Your server confirms the result through the Merchant API before you fulfil the order.

Requirements

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.

Why it matters. Script attacks (also called e-skimming or Magecart) inject or alter JavaScript on a checkout page. On a page that embeds a payment iframe, a malicious script can replace the iframe with a fake form or overlay one on top of it. The cardholder then types card details into the attacker's form.

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

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

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

Your requirements

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.

Never send 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

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

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

What to do

  1. Contact Paytrim at itoperations@paytrim.com.
  2. 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.
  3. 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.
  4. 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.

Sources

Last updated 2026-11-13. This page may change as PCI DSS and Paytrim's services evolve.

« Back to documentation