If you are encountering unusual issues with our Accept Stripe Payments plugin that other sites do not seem to experience, it is advisable to consult this document in conjunction with the Common Troubleshooting Resources page.
If you previously used a plugin or platform that set up your Stripe account, it likely employed ‘Stripe Connect’. This method involves on-boarding you as a customer and acting as an intermediary for API calls to Stripe. Suitable for multi-party integration, ‘Stripe Connect’ enables third-party transactions and permits the addition of transaction fees if selected. All API keys and credentials generated during the plugin’s on-boarding process are managed through their platform. For detailed information, please refer to the Stripe Connect documentation:
Unlike these plugins, our ‘Accept Stripe Payments’ plugin integrates directly with Stripe. This direct integration enables you to process payments from your customers without intermediaries. You will create a standard Stripe account on your own, copy the API credentials from your Stripe account, and then input these details into our plugin’s configuration.
However, if your account remains connected to another platform, you may experience unusual behavior due to the platform’s selection of specific API versions. This could mean that API calls are routed to an older or different API version, leading to varied responses.
We recommend generating completely new API keys for use with our plugin. It’s important to note that if your account is linked to a third-party platform, the routing of API calls might still involve that third party. Further investigation is needed to fully understand the implications of an account created via ‘Stripe Connect’ versus a standard Stripe account. For more on the types of accounts facilitated through Stripe Connect setup, visit: