Sep 09, 2021

Updated Stripe Integration Information

Who is Stripe for (target market)?

  • European customers who need to be SCA compliant
  • Any operator who can and wants to use Stripe as a payment gateway

What are the differences from this updated Stripe integration to the old?

On the new updated Stripe integration, we have updated it to the new Stripe integration which will tokenize the Credit Card with Stripe. This means that any newly added Credit Cards or previously entered Credit Cards will need to be entered on the updated Stripe integration again so it can be tokenized and saved.

Once a Credit Card is tokenized with Stripe, then you can use that Credit Card for processing on the new Stripe integration as you normally do now today (Auth, Auth & Capture, Pr. Capture, Void, Credit).

What is Strong Customer Authentication (SCA)?

Strong Customer Authentication (SCA) is a European regulatory requirement to reduce fraud and further make online payments more secure. Strong Customer Authentication (SCA) applies to online payments within Europe where both the business and the cardholder’s bank are located in the European Economic Area (EEA), United Kingdom, and Switzerland.

Credit Card payments require a different user experience and flow, namely 3D Secure, in order to meet SCA requirements.

What is 3D Secure?

For extra fraud protection, 3D Secure requires customers to complete an additional verification step with the card issuer when paying with their Credit Card online. Typically, you direct the customer to an authentication page on their bank’s website, and they enter a password associated with the card or a code sent to their phone.

The Strong Customer Authentication regulation in Europe requires the use of 3D Secure for card payments. 3D Secure is optional in other regions but can still be used as a tool to reduce fraud and chargebacks.

Think of this as a form of 2 Factor Authentication.

If this is a regulation for Stripe in Europe, why is it affecting Stripe users in the United States?

In today’s age of online credit card payments and processing, more and more standards and security measures are being put into effect to better protect the consumers and merchants. These standards are aimed at reducing fraud and further making online payments more secure.
We are starting to see 3D Secure on more transactions in the US. This implementation also prepares you and Limo Anywhere for any future regulations that may come with Credit Card processing in the future in the US.

It is good practice to capture as much information, like Billing Address, when processing payments. This not only further protects your customer but it can protect you and your business from potential fraud and chargebacks.

What are the benefits of this new Stripe Integration?

  • Up-to-date protocols/regulations with improvements to reduce fraud including 3D Secure.
  • The ability to capture payment on ORES at the time of booking (coming soon.)
  • Secure way for operator to capture the customer’s Credit Card online (Request Payment option.)
  • More data passed over to Stripe.

Can I request payment information from my customer?

Yes, you can. In cases where the credit card is 3D Secure, you will need to request payment information in order for your customer to authorize the transaction. You also can use this feature to securely capture the Credit Card # directly with ANY of your customers with Stripe online without having to take this information over the phone.

Why can I not view the Credit Card number for my Stripe entered cards?

Since the card is tokenized and stored with Stripe, Limo Anywhere does not have the Credit Card number to view. You will be able to view Credit Cards on previously entered Credit Cards or non-Stripe Credit Cards if needed. You will need to send in request to view Credit Cards by email to support@limoanywhere.com.

Why can I not process a payment with previously entered Credit Cards?

The Credit Card must be tokenized and stored with Stripe in order to process the payment. The previously entered Credit Cards have not been tokenized with Stripe.

What are the mandatory fields for processing Credit Cards through Stripe?

Currently the mandatory fields are:

  • Name
  • Credit Card Number
  • Expiration Date
  • CVC/CVC

Of course it is best practice to get as much information as you can when processing credit cards.

Will my previous transactions on Stripe be able to be Captured, Voided, Credited in LA on new Stripe integration?

No, these will need to be handled and processed on the gateway side and then recorded in LA without going through the gateway.

Links to Articles

Coming Soon for Stripe

  • Automatic payment processing at the time of booking on ORES.
  • Ability to automatically send payment request when a transaction has been declined.
  • Ability to request payment for existing stored cards on an account.