Your payments.
Your control.
How Travede protects payment data, and how responsibility is shared between us, you, and your payment providers.
Tokenization
Tokenization replaces payment credentials with a reference used for supported payment activity. Your team works with tokens, not stored card details.
Vaulted separately from your gateway
Card details are kept in a secure vault, independent of your gateway, so you keep control as you route through supported providers.
Safeguards
Travede maintains reasonable administrative, technical, and physical safeguards appropriate to the data it handles, with access limited to people who need it.
Shared responsibility
Each party meets the PCI DSS and payment-security requirements for its role. Tokenization doesn’t eliminate a merchant’s own obligations.
Incident notification
If a security incident materially affects your protected data, we’ll notify you without undue delay and work with you on containment and any required notices.
Compliance & attestations
Card capture and tokenization run on PCIVault (pcivault.io), an independent PCI DSS v4.0.1 validated Level 1 service-provider vault, assessed annually by a Qualified Security Assessor. Card numbers are entered into the vault’s hosted fields and charged token-in, token-out through its proxy; Travede systems store only the token, the first six and last four digits, expiry and cardholder name, never the full card number. Travede maintains its own PCI DSS service-provider self-assessment. A current PCI DSS certificate of compliance for PCIVault, and its Attestation of Compliance under NDA, are available to customers on request.
Found a vulnerability?
Report it to support@travede.com with steps to reproduce. Don’t include real cardholder data.