Hi there,

It wasn't that long ago when we added Stripe. I believe it was 9.0.5, so it should be working.

I've linked the help instructions below. Be sure use one of the testing credit cards when you are in a test mode.  

https://help.ablecommerc...%2FGateways%2FStripe.htm

Stripe Test Credit Card numbers

Visa 4242424242424242 (no authentication required for std US card)
Visa 4000002760003184 (triggers authentication as required)

Please let me know if this solves the issue.

P.S. 9.0.5 came out Sept 27, 2021.

That's forever in ecommerce/PCI compliance time!!

I understand, and expected as much.

I did have debug enabled, and I didn't find a stripe log file in the app_data\logs folder.

I did see the error both on the AC side, and on the Stripe dev dashboard side.

Looking closer in the logs folder, I see it in app.log. Perhaps the exception chain will help you?

---
2024-02-15 13:46:17,949 ERROR AbleCommerce Provider threw exception in DoAuthorize.
Stripe.StripeException: Sending credit card numbers directly to the Stripe API is generally unsafe. We suggest you use test tokens that map to the test card you are using, see https://stripe.com/docs/testing. To enable raw card data APIs in test mode, see https://support.stripe.c...s-to-raw-card-data-apis.
at Stripe.StripeClient.ProcessResponse[T](StripeResponse response)
at Stripe.StripeClient.<RequestAsync>d__25`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Stripe.Service`1.<RequestAsync>d__26`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Stripe.Service`1.Request[T](HttpMethod method, String path, BaseOptions options, RequestOptions requestOptions)
at Stripe.PaymentMethodService.Create(PaymentMethodCreateOptions options, RequestOptions requestOptions)
at CommerceBuilder.Payments.Providers.Stripe.StripeProvider.DoAuthorize(AuthorizeTransactionRequest authorizeRequest)
at CommerceBuilder.Services.PaymentService.Authorize(AuthorizeTransactionRequest request, IPaymentProvider paymentProvider)
---

The page works for me. Try it without the trailing period:

https://support.stripe.c...ss-to-raw-card-data-apis

It basically says you can use it in production if you can prove PCI compliance. In test they can do it without proof, but that doesn't really help.

I'm not really interested in making it harder to be PCI compliant! :) And it certainly doesn't meet the qualifications of a "payment gateway".

It'll probably fix it, however without direct guidance and documentation from AC on how to prove to Stripe that we're PCI Compliant, this is a no go for us.

Our setup is a bit unique in that we also take "card present" payments, not just online.

I looked at Braintree earlier and they were online only?

I'm not sure what to make of this warning message.

When we develop integrations with payment gateways, the credit card information 'can' be stored in AbleCommerce, using encryption of course. On purchase, the card info is passed to the API, but that is over a secure channel. It seems that Stripe does not prefer this type of integration because of the liability the merchant has to keep the card data safe.

With the link I provided to qualys.com, and the help of their online system, it's not too difficult to get PCI approved. The basic steps are to first run a scan on your website. A report is generated. Then you start fixing any the security issues that are ranked high. Run the scan again to confirm all the P1 issues are taken care of. (It might take a few attempts to get them all)

Then you have an official scan to provide the payment service. You'll also have a questionnaire to complete. Most of it has to do with your internal procedures for handling credit card info.

Before you make any decisions, let me have quick discussion with the dev team. We have a new integration coming in the next version, and I want to check and see exactly what it covers.

Got it on the PCI compliance.

This morning, our devs confirmed that Stripe is working using the current API supported in Able.

Be sure to use the 4242424242424242 for the test card.

FYI - We are implementing Stripe POS in the next version of Ablecommerce. It will handle inventory updates and payments.

It's working in our test environment. I have to assume you will need to enable the option and be PCI compliant if you want to use our integration with Stripe. Enabling this option in your test environment would be a confirmation.



Sorry, I meant SQUARE POS, not Stripe. I can get a better description of the features from our devs next week. We hope to have 9.0.10 by end of next month, or into first part of April....depending on how final QA goes, and final testing should be starting in about 2 weeks.

Hi Charles,

I opened an issue report with the dev team. If we have time to get it in, then it will be available in the next release. Otherwise, we can provide an updated Plugin soon after.

Thanks!