Please note that when using the Stripe option, you won't be able to have a gateway enabled under the Let Customers Pay with a Credit or Debit Card option, since the Stripe option shows a credit card form within the checkout already, and only one is allowed on the checkout at a time. Don't worry though - customers will be able to pay with Credit and Debit cards through the Stripe payment fields.
As part of the configuration for Stripe in the Foxy admin, it's also possible to specify a statement descriptor suffix, which will be appended to the statement descriptor as set in your Stripe configuration which appears on your customers card statements.
This can be set using the optional “statement descriptor suffix” field within the Stripe settings on the “payment” section in the Foxy administration. The statement descriptor can be a maximum of 22 characters in length - which includes the descriptor already set on your Stripe account, and 2 additional characters of *
. This means that if your statement descriptor was MYSTORE
, you would have 13 characters for your suffix. If you set the statement descriptor suffix to CUSTOM-SUFFIX
, the descriptor on the customers card statement would show as MYSTORE* CUSTOM-SUFFIX
. See this page on Stripe's documentation for more details.
If your store is currently making use of one of our older Stripe integrations, or another debit/credit card based payment gateway, you will need to update your store to switch over to the new Stripe integration. You can follow these steps to complete that.
At this point, your store has been successfully updated to use our Stripe integration.
If you have set your checkout template to “Custom Template”, and embedded the raw checkout.inc.twig
template directly, or have embedded the payment_method
Twig block, you will need to update your checkout template with some new code for Stripe. You can reference the current iteration of the checkout template on Github here.
Stripe is continually expanding the countries that they support. The good news is, FoxyCart's existing Stripe integration should support any new countries that they do add support for. For a list of the countries that Stripe currently support, see this page on their site.
As of Foxy v2.0, the “Order ID” that Foxy passes to Stripe (which is normally the Foxy transaction ID) can be overridden. This is considered advanced functionality, and is only relevant for very specific use cases (such as complex fulfillment processes where multiple authorizations and captures may need to be grouped by the Order ID).
To override the default Foxy transaction ID, add an ''attribute'' via the API named fx_transaction_id_gateway_override
, to the cart
resource. The value of that attribute will be passed to Stripe as the Order ID.
For configuring a test account with Stripe, you can simply complete the same process as detailed above, but leaving your payment servers set to “Test Servers”. When you click to connect to Stripe, on the following page will be an option at the top of the page to “Skip this step”, which will bring you back to Foxy with a test Stripe account connected and ready to use.
You can use 4242424242424242 to simulate successful card validations in test mode (this number fails in production of course).
Technically, any card number that passes the Luhn Check will validate successfully in test mode – this includes real credit card numbers. You might not want to use real card numbers while testing though, to avoid accidentally checking them into your codebase.
The following are also true in test mode:
To simulate the 'Card Declined' error use this special card number - 4000000000000002.
Contact stripe for info. Know more? Feel free to edit this page with info.
If you have tips, experience, or helpful notes related to this gateway that would benefit others, please add them below, including your name and the date. We reserve the right to edit or remove comments that don't add value to this page.