When you start using PCI Booking, you probably already have a process in which you capture credit cards. This also means that you probably have a database of stored credit cards that will need to be migrated to PCI Booking.
Our Store method allows customers to submit the cards stored in their system into PCI Booking and receive, in the response, the card token for this card.
- Authenticate PCI Booking using your API Key, an "access token" or a "session token". Read more about our authentication methods.
- Retrieve the card details from your database and prepare the request body in our card data XML structure
- Send the request to PCI Booking.
- The response will include the card token in a header value called
Locationand the masked card details in the response body.
- Store the information from the response - none of the information returned falls under PCI scope so you are able to keep it all.
- Delete the card that was stored in your database.
- Optionally, set the CVV Retention Policy for this token.
Migrating multiple cards
The Store method is designed for submitting one card. In most cases, you would have many cards to migrate over to PCI Booking. In that case, you would have to loop the above process multiple times for each of the stored cards.
Updated about 3 years ago