Release

Search

Data protection

Link copied to clipboard

On this panel, you can define whether CVV verification is required and what type of information PortaBilling stores (token or full card info except the CVV).

Data protection panel

CVV required

Link copied to clipboard

When you create a merchant account, connected with a payment processor, you can set it to check the card security code. If you did it there, you should also enable it in PortaBilling.

Turn on the CVV required toggle switch if a card security code is required for payments via this processor.

When a card security code (CSC, CVV, etc.) is required for every transaction, the configured auto payments are rejected by the payment processor since PortaBilling doesn’t store such codes and therefore can’t automatically pass them to the payment processor when payments are made. Consequently, repeated unsuccessful payment attempts only create an additional load on the system. To avoid this, when the CVV Required option is enabled, PortaBilling discards all previously configured auto payments via this payment processor.

Stored card information

Link copied to clipboard

Choose what information PortaBilling must store:

  • Token only — PortaBilling stores only the token received from the payment processor. The processor generates the token when a user performs a transaction with a card for the first time. The user enters all the card information, including the CVV code, only once. Any further transactions don’t need additional CVV verifications. For the full list of currently available payment processors that support token-based payments in PortaBilling, refer to  Supported online payment processors section.
  • Full card info except the CVV — this is a default option. PortaBilling stores all card information except for the card security code, which can’t be saved for security reasons.
See Also

On this page

Release
What's new
Admin manuals
Handbooks
API
UI help
Search