Stripe

Do I need to have a Stripe account?

No, we work with all processors and a Stripe integration is not required. Do note, some of our functionality is only available with Stripe currently (billing descriptors etc.)

Stripe Integration Instructions

1. Create a new restricted API key in Stripe (https://dashboard.stripe.com/apikeys) ensuring that all the required permissions (see the full list below) are selected.

2. Grab your Stripe account ID from your profile page (https://dashboard.stripe.com/settings/user).

3. Login to ChargebackStop and under Settings > Integrations add your Stripe account ID and restricted key.

Stripe Integration Permissions

Permission	Description
Charges (Read and Write)	Required for matching network alerts to charges and processing refunds.
Customers (Read)	Essential for linking alerts to customers and accessing payment methods.
Events (Read and Write)	Ensures real-time updates on account changes without the need for frequent resource refetching.
PaymentIntents (Read and Write)	Used for correlating network alerts with charges and initiating refund processes.
⁠PaymentMethods (Read)	Helps match network alerts by analysing the BIN on card objects.
Products (Read):	Provides necessary information related to payment intents and subscriptions.
Prices (Read)	Displays information pertinent to subscriptions.
Subscriptions (Read and Write)	Facilitates the linking of payment intents to invoices, supporting refund and cancellation workflows.
Credit notes (Read and Write)	Enables viewing and managing invoice refunds when using Stripe Billing.
⁠Invoices (Write)	Allows for linking payment intents to their respective subscriptions and updating statement descriptors for Link payments.
Webhooks (Write)	Allows for ChargebackStop to setup webhooks for the platform to automate certain tasks in real time.

What is synced?

In order to match network alerts to your Stripe transactions and automate refunds, we need to sync the following data into our system:

→ Payment intents / charges

→ Customers

→ Refunds

→ Subscriptions

→ Payment methods (without card numbers)

→ Last 4 digits of card number

→ BIN

→ Disputes

→ Early fraud notification

Matching Stripe Link payments

Without a change to the default Link settings with Stripe your coverage may be impacted and we may not be able to prevent as many chargebacks. It may also result in charges for unactionable alerts.

Please read this section carefully to understand what change you need to make.

If you use Stripe Link as a payment method in your Stripe integration, we won't be able to automatically match alerts to Stripe transactions. Stripe made the decision to not disclose card brand, card last 4, authorisation code, BIN, or ARN for transactions paid for with Link in their API.

If you still want to offer Link to your customers, we recommend using it in wallet mode. Read more details in Stripe documentation ("Link with card integrations" tab).

If we cannot match an alert due to multiple matching Link transactions existing, you might still be charged for the alert. This is not a valid creditable scenario recognised by Verifi nor Ethoca.