Quick start
Mount the PCI Component on your checkout for one-shot tokenized payment with a new
card, in Hybrid mode (mode: 1). Sensitive fields never touch your DOM (PCI-DSS compliant).
This quick start stays on Hybrid + new card. For Complete / Mixed, saved cards,
external_reference, and CVV retry after a declined charge, see
Saved cards and modes.
For the full flow (sequence diagram, environments, sandbox), see Geopagos PCI Component.
Environments
| Environment | CDN ({cdn_host}) | API ({api_host}) |
|---|---|---|
| Staging | pci-card-form.stg.geopagos.io | api.stg.geopagos.io |
| Production | Provided by Geopagos | Provided by Geopagos |
Mount
sessionId comes from your backend (POST /api/v1.0/sessions on https://{api_host}/api/v1.0).
const { Checkout, CheckoutError } = await import(
'https://{cdn_host}/v1/main.js'
);
const form = new Checkout(sessionId, {
onSubmit: async () => {
await fetch('/checkout/charge', { method: 'POST' }); // your backend + JWT
},
onError: (error) => console.error(error.toJSON?.() ?? error),
});
await form.render('card-form-container');
The session_id is the only thing your page hands to the component. The public key, the
enabled card brands, the payment methods and every buyer-facing text are fetched by the
component from the BFF — never passed from your page. That is provenance, not secrecy: a
hostile script on the host page must not be able to swap the encryption key.
Where to go next
| Guide | What it answers |
|---|---|
| Embedding the component | How to load it, mount and unmount it, TypeScript, browser support |
| Configuration Object | Every option and method: selector, theme, errorDisplay, collectEmail, setTheme() |
| Lifecycle Hooks | The six callbacks, what each one fires on and what it carries |
| Error Handling | CheckoutError, every code and what to do about each |
| Backend Integration | Creating the session and running the charge from your server |
| Saved cards and modes | Modes `0 |
| Security | What stays on your server versus the browser |