Resolve Stripe Errors as a Seller

If you have successfully connected Stripe, but you or your customers are encountering errors during checkout, it is usually related to your Stripe account configuration or restrictions. In this article, we'll go through some of the most common Stripe errors and what they mean.

Understanding Stripe error messages

1. This Connect account cannot currently make live charges

In many cases, this happens when the Stripe account is still in test mode or when the account setup and verification process has not yet been fully completed. Until Stripe enables live payments on your account, customers will not be able to successfully complete purchases.

How to resolve: We recommend contacting Stripe support directly, as they can review your account, confirm whether any verification steps are still pending, and help you enable live payments.

2. Apologies cannot complete the transaction (E19)

E19 is one of the most common payment processing error codes. It typically means the payment system could not determine exactly why the transaction failed. It can be triggered by a number of things: a card authorization issue, a temporary network hiccup, or a general processing problem on the payment processor's end.

How to resolve: The best first step is to try the payment again, ideally in a different browser or in an incognito or private window.

3. The account isn't enabled for cross-border transactions

This means that for that specific payment, your Stripe account is currently unable to process payments from customers located in certain countries. 

How to resolveIn this case, the best option would be to offer the customer an alternative payment method to complete the purchase.

Need more help?

If you're running into a Stripe error that isn't covered in this article, please contact our support team at contact@payhip.com and include the error message you are seeing, along with a screenshot, so we can investigate further.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.