What problem does it solve?
It prevents payment connectors from violating PCI DSS by incorrectly handling credit/debit card data, Secure Proxy routing, logging, and storage during authorization flows.
Core Features & Use Cases
- Secure Proxy routing for non-PCI environments: Ensures connectors hosted outside PCI environments (including VTEX IO apps) must use
secureProxyUrl and forward correctly to the acquirer with required X-PROVIDER-Forward-* headers.
- Authorization-only Secure Proxy constraint: Clarifies that Secure Proxy applies only to Create Payment (card authorization) and not to cancel/capture/refund, which must use direct PSP API calls.
- Card data handling guardrails: Enforces strict rules to store only safe metadata (e.g.,
card.bin, card.numberLength, card.expiration) and to never store or log raw card details or token values.
Quick Start
Use this skill to audit or implement your payment connector’s Create Payment handler so that it routes via secureProxyUrl in non-PCI contexts while keeping raw card data out of storage and logs.