Card Vaulting

introduction as part of our payment optimization suite , forter offers agnostic card vaulting solutions that work across all processors to protect sensitive card data by replacing it with secure tokens improve payment performance by reducing fraud and increasing approval rates maintain full control over card data while ensuring compliance with pci dss standards our suite includes pci tokens network tokens account updater these solutions help you optimize your payment stack while tailoring your compliance needs to your business model image benefits of forter tokenization agnostic tokens – enabling multi processor strategy zero pci scope – eliminate the need to build and maintain a pci certified vault, saving resources, costs, and compliance efforts processor flexibility – tokenized card data can be used across multiple payment processors enhanced security – protect sensitive card data, reducing the risk of fraud and data breaches seamless integration – work with any processor, ensuring full payment ecosystem flexibility choosing the right tokenization approach when implementing forter tokenization solution for your project, select only one of the available approaches outlined in this documentation zero pci scope docid\ u0wxal1dj9ykbgbdq5ksr (recommended) who is it for? merchants who want to avoid handling card data entirely compliance scope forter fully handles compliance how it works forter collects and tokenizes card data before it reaches your system implement forter’s hosted fields on your checkout page receive a single use token when the customer submits payment process transaction using the token upgrade to a multi use token for recurring payments via the upgrade api limited pci scope docid\ nobylqryl 3gckfjcoobg who is it for? psps & merchants who are already pci compliant but want to reduce scope compliance scope you retain some compliance responsibilities how it works you collect card data but tokenize it through forter's api collect card data in your front end (checkout window), but send to forter to receive a pci token before storing in backend forter passes card data via detokenization proxy to processor(s) when needed (i e , in authorization step) which one to choose? if you don't want any pci liability , choose zero pci compliance if you already have pci compliance but want to minimize exposure , choose limited pci compliance components zero pci compliance forter handles the entire process, so you never touch raw card data detokenization proxy docid\ d8uveyrulesc57ikqbnqr passes card data to third party services without exposing raw card details hosted fields sdk docid\ p8fdu6mlzmduel8qpjek collects card data securely on the checkout page and returns a token limited pci compliance you collect card data but reduce pci scope with forter’s tokenization api tokenization api docid\ zmi5csng4 rhy sr1bgn7 replace sensitive payment data with non sensitive tokens additional payment optimization features in addition to pci tokenization, forter's card vaulting solution also offers network tokenization https //docs forter com/tokenization api reduce processing costs & improve approval rates using network issued tokens account updater https //docs forter com/account updater api automatically update expired or replaced cards for seamless transactions