Setting/ownersccsecurity: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (6 intermediate revisions by 4 users not shown) | |||
| Line 3: | Line 3: | ||
Best practice for credit card security is not to store the card CCV number with the other card details. | Best practice for credit card security is not to store the card CCV number with the other card details. | ||
''' | '''Email CCV''' sends an encrypted Security Code in the host booking notification email. The CCV is not stored. The Credit card and CCV can only be viewed '''once''' by entering the encrypted security code into the booking details. | ||
*If you use Payment Gateway > Credit Card Collection and Booking Type = Confirmed/Request with Credit card, then the Credit card details will be stored in PCI Secure database and can be viewed only once. | |||
'''Do not store cards''' discard credit cards without storing them. Use this option if you must conform with PCI DSS regulations not to store cards online. | *If you use Payment Gateway > STRIPE and Booking Type = Confirmed/Request with Credit card, then you can use the 'Send credit card to Stripe' button in the Charges & Payments tab of the booking. | ||
'''Do not store cards''' discard credit cards without storing them. Use this option if you must conform with PCI DSS regulations not to store cards online. If you have chosen to send cards to Stripe they will still send. | |||
'''Store CCV''' DEPRECATED | |||