What is Vaulting?

​

When a credit card is entered into Jackrabbit, it is immediately replaced with a random set of numbers assigned by the Org's gateway. This process is called Vaulting. The new set of numbers is called the VaultID. The original credit card # is no longer kept on the Jackrabbit servers and the Org is now considered PCI Compliant.

​

Things to Know about Vaulting

• Vaulting occurs when the credit card is first entered in Jackrabbit, not necessarily when it is first processed for payment.
• VaultIDs are gateway specific. This comes into play when an Org is considering switching payment processors or are Multi-Location, Multi-Gateway setups (see below).
• All active gateways vault.
• Editing/updating a credit card # is allowed for all vaulting gateways EXCEPT Studio Autopay. Studio AutoPay is vaulted differently and does not allow updates or edits to a credit card # (see below).

  ​

Multi-Location eCommerce and Vaulting

Credit cards are vaulted to a gateway. Which means if an Org is a Multi-Location, Multi-Gateway, an Org cannot just change a family location and expect their credit card to process correctly. It must be re-vaulted to the correct gateway. They must delete the credit card, change the family location and then re-enter the card # in order to re-vault the card. To determine if the Org is Multi-Location, Multi-Gateway, look at their Admin eCommerce settings ...

If an Org is Multi-Location, Single Gateway, then the Org can change the family's location and their credit card will process correctly.

Studio AutoPay/ACH Direct/Forte

When VaultIDs are entered for SAP Orgs, they are visually different from the others. There are actually two sets of numbers. Additionally, Studio AutoPay does not allow a credit card to be edited or updated (even the expiration date). In all cases, it must be deleted and re-entered.

​

Page Last Updated: 4/16/2019 9:32 AM
Jackrabbit Technologies