Webhooks are useful as they allow us to receive updates about transactions processed.
This can be configured in the Stripe dashboard by creating an event destination.
Please enable Stripe webhooks only for the following events, to ensure
minimal delays in processing at our end.
The Stripe connector can operate as either an open or a closed-loop connector. In
a closed-loop configuration we will use a Stripe token for every transaction, which means you can not process a subsequent payment with another provider.In an open-loop situation we will use card data from our vault for every transaction, allowing us to processing transactions in a recurring
payments with a different payment service for every transaction.By default, your Stripe connector will work in a closed-loop configuration, as Stripe requires open-loop to be enabled for your account
before we can process transactions that way. Please contact our support team for additional guidance.
Recurring Apple Pay and Google Pay are supported through Stripe in a close-loop configuration. For this to work we will require you to contact Stripe to
get decoded Apple and Google Pay token pass-through enabled on their /v1/tokens API. We currently do not support recurring digital wallet payments on
Stripe in an open-loop configuration as this requires a different Stripe API. We are looking to add this in the near future.
Our integration replies on the ability to pass Stripe the full card PAN. If you encounter an error
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 testing raw card data APIs, see https://support.stripe.com/questions/enabling-access-to-raw-card-data-apis.,
please contact Stripe’s support team to enable raw card data API.
If you encounter an error statement_descriptor parameter is not supported for the payment_method_type card,
please contact your Stripe technical account manager to enable this feature.