Security
What an integrator needs to know for tokenized payment with the PCI Component. Internal hardening details of the BFF are out of scope here.
Trust model
| Step | Who | Auth |
|---|---|---|
| Create session, charge, list/delete payment methods | Your backend | Bearer access token from the Geopagos identity provider |
Form runtime (config, payment/intent, …) | The PCI Component (CDN) | X-Session-Id only — not part of the integrator API |
See Backend Integration → Authentication for how to
obtain the token and when to send merchant_id.
- Never put your access token or your client credentials in the browser.
- In Hybrid/Complete the card token never returns to your page:
payment/intentanswers204andonSubmitcarries no card payload. In Mixed, the saved card's public fields (with itspayment_method_id) appear inonSubmit.result— still no PAN/CVV. - Treat
session_idas a capability: do not log it broadly; limit it to the page that mounts the form. Alone it cannot charge or soft-delete a wallet (JWT required). - CVV never travels on
POST /payment. After a declined charge with a saved card, remount the same session ifretry.allowedis true — see Saved cards and modes → CVV retry.
What the host must not do
- Pass public keys, amounts or card brands into the SDK from your page — the component loads them from the BFF.
- Call
POST /paymentfrom the browser. - Soft-delete saved cards from the browser (DELETE requires your Bearer token).
- Create a Mixed session without the buyer’s consent to store the card: in Mixed, submitting the form saves it.
Encryption
PAN, expiration and CVV are entered in separate cross-origin iframes and encrypted there with JWE before leaving the iframe. Your DOM never sees plaintext card data.
Bot protection
When it is active for the environment, the component runs an invisible reCAPTCHA v3 check each time the buyer presses the submit button, and the BFF validates it before accepting the payment intent. There is nothing to integrate:
- It runs inside the component's iframes, so your page's Content Security Policy does not change.
- The buyer never solves a challenge. Instead of Google's floating badge, the form shows a short notice with links to Google's Privacy Policy and Terms of Service; its text is part of the merchant's configuration, like the rest of the form's texts.
- If the check fails, the component closes itself and
onErrorreceivesCAPTCHA_REJECTEDorCAPTCHA_UNAVAILABLE. The session is still usable — see Error Handling.
Related
- Backend Integration
- Saved cards and modes
- Embedding
- Error Handling — issuer declines arrive on the charge, not in the form