...
By default, the Field Type will be set as Token for the credit card number and CVV fields.
| View file | ||
|---|---|---|
|
...
Important things to know when setting up your form:
...
Do I need to update P2P pages?
No.
How can I customize the alerts for field validation?
This is controlled from the “Alerts and Validators” page -> Alerts section.
What if I only have digital wallets on my page?
No impact as this is only for credit cards.
Will the format for my export look the same?
Yes, and you will still see the credit card brand used by the donor.
Do I need to empty CC/CVV fields if donor switches to another gateway?
You don’t need to empty the fields as long as you are hiding the credit card fields either using page dependencies or “display:none” if using custom code.
How will this impact my existing tokenization set up with my payment gateway?
Tokenization at the gateway level (like Vantiv) is not impacted by VGS and will continue to work like it does now.
Will the autoresponder merge tag for “last 4 digits of credit card” still work?
Yes.
Now that CVV is required, how can I handle forms that don’t need a CVV value?
For use cases where CVV is not required, the client can simply remove the field from the form block.