I'm currently integrating with Stripe [1] to handle subscriptions to a SaaS product.
I would like to create a minimal form for collecting credit/debit card details.
With respect only to charging a user for a subscription, the details I need are that of the card: card number, expiry date and card verification code. The collection of these fields alone is sufficient for charging a card.
I am concerned that the fewer details collected in the payment form, the greater the chance of a given transaction being fraudulent.
Instead of collecting cardholder details (name on card, billing address) what measures, preferably technological, can I take to reduce and/or minimise fraud?
In other words, what behind-the-scenes, automated measures can I put in place to reduce fraud without having to ask the user for anything other than the credit card number, expiry date and cvc?
[1] http://stripe.com/
I would like to create a minimal form for collecting credit/debit card details.
With respect only to charging a user for a subscription, the details I need are that of the card: card number, expiry date and card verification code. The collection of these fields alone is sufficient for charging a card.
I am concerned that the fewer details collected in the payment form, the greater the chance of a given transaction being fraudulent.
Instead of collecting cardholder details (name on card, billing address) what measures, preferably technological, can I take to reduce and/or minimise fraud?
In other words, what behind-the-scenes, automated measures can I put in place to reduce fraud without having to ask the user for anything other than the credit card number, expiry date and cvc?
[1] http://stripe.com/