Skip to main content

​
Sign-up

Stripe provides a self-service sign-up for a sandbox account. To sign-up for an account visit the sign-up page and fill in the details.

​
Credentials

When setting up Stripe in the dashboard, you need to configure the following credentials, which are obtained from Stripe:

​
Secret key

The Stripe Secret key can be found in the Stripe Admin Portal under the Developers -> API Keys section. Stripe Secret key

​
Webhooks

Webhooks are useful as they allow receiving 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.
  • payment_intent.canceled
  • charge.expired
  • charge.refund.updated
  • charge.refunded
  • payment_intent.succeeded
  • payment_intent.amount_capturable_updated
  • payment_intent.payment_failed

​
Recurring payments

The Stripe connector can operate as either an open or a closed-loop connector. In a closed-loop configuration a Stripe token is used for every transaction, which means you can not process a subsequent payment with another provider. In an open-loop situation card data from the vault is used for every transaction, allowing processing transactions in a recurring payments with a different payment service for every transaction. By default, your Stripe connector works in a closed-loop configuration, as Stripe requires open-loop to be enabled for your account before transactions can be processed that way. Please contact the support team for additional guidance.

​
Digital wallets

Recurring Apple Pay and Google Pay are supported through Stripe in a close-loop configuration. For this to work you need to contact Stripe to get decoded Apple and Google Pay token pass-through enabled on their /v1/tokens API. Recurring digital wallet payments on Stripe in an open-loop configuration are currently not supported as this requires a different Stripe API. Support for this is planned for the near future.

​
Gated features

Stripe gates certain features on the platform. In case the following errors are encountered, please reach out to Stripe as mentioned below.

​
Access to raw card data

The integration relies 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.

​
Use of statement_descriptor field

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.