Stripe
Last updated
Last updated
ChargebackStop is a trading style of Jade Technologies Limited (company number: 15043871). Registered at 7 Bell Yard, London, England, WC2A 2JR.
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.)
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.
Grab your Stripe account ID from your profile page (https://dashboard.stripe.com/settings/user)
Login to ChargebackStop and under Settings > Integrations add your Stripe account ID and restricted key
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
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 (Read)
Allows for linking payment intents to their respective subscriptions.