|
Purpose
Starting with version 2.4, H-Sphere requires that users creating credit
card billing profiles enter CVV (card verification value) to prevent fraudulent signups.
Merchant gateways supporting CVV verification approve the credit card.
If the credit card is rejected, the billing profile is not created.
Security
H-Sphere doesn't store verification values. Once the billing profile
has been created, H-Sphere assumes that the credit card is valid and doesn't supply
verification values with subsequent credit card transaction requests.
Gateways supporting CVV
CVV is implemented in the following gateways:
AuthorizeNetSIM
Innovative
NetBilling
MainStreetSoftWorks
PayMeNow
Protx
Tucows
Gateways that don't support CVV verification are sent transaction requests without verification
values (as in H-Sphere before 2.4).
CVV Configuration
By default, credit card verification is usually disabled,
which means all cards are automatically accepted. CVV settings can be configured in the
merchant gateway's interface. Make sure to allow transactions without verification
values, because H-Sphere sends verification values only when creating billing profiles.
|
