Last modified: 24 Dec 2007
WARNING: This documentation covers Parallels H-Sphere versions up to 3.1. For the latest up-to-date Parallels H-Sphere documentation, please proceed to the
official Parallels site.
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.
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.
When a new signup is moderated, H-Sphere verifies the CVV and marks it as
'Verified' (verification successful) or 'Not verified' (verification failed).
Based on this information you can choose whether to create or delete the account
in the moderation list.
By default, credit card verification is usually disabled,
which means all cards are automatically accepted. To enable CVV verification:
- Go to Settings->Signup Guard
- Check CVV Validation and click Submit Query.
CVV settings can be configured in the merchant gateway's interface (not in H-Sphere).
Make sure to allow transactions without verification values,
because H-Sphere sends verification values only when creating billing profiles.
Gateways that don't support CVV verification are sent transaction requests
without verification values (as in H-Sphere before 2.4).