Stripe
Integrating Stripe with Osano
Connecting to Stripe
In order for Osano to discover data stored in your systems, we must connect to those data providers via an API. We require, at minimum, read-only access to establish a connection to these providers. Each provider you connect may require different information. Please see the linked vendor documentation for instructions on where and how to obtain this data.
Required Fields
- Auth Token
Instructions for obtaining your Stripe Auth Token.
Required Scopes
When creating restricted keys for Stripe (Developers -> API Keys -> Create Restricted Key), you will need to select the following permissions:
Resource Type | Permission (None, Read, Write) |
---|---|
All Core resources → Customers, Charges, and Disputes | Read |
All Checkout resources → Checkout Sessions | Read |
All Billing resources → Invoices | Read |
All Orders resources → Orders | Read |
Note: Please ensure your Stripe version is set to 2020-08-27 or later in the Stripe Developer Dashboard for user search.
Core Functionality
- Data Discovery
- User Search
- Data Deletion
Base URL
Auth
- oauth
- apiKey
Bearer authentication with API Key
User Search
- name
- phoneNumber
- address
- birthday
- userId
Endpoints
Used for data discovery
- GET
/customers
- Expanded sources, tax ids, subscriptions, and default sources
- GET
/orders
- GET
/charges
- GET
/checkout/sessions
- GET
/invoices
- GET
/disputes
- GET
/refunds
Used for user search
- GET
/customers/search?query=email:"$email"
- Expanded sources, tax ids, subscriptions, and default sources
- GET
/orders?customer=$customerId
- GET
/charges?customer=$customerId
- GET
/checkout/sessions?customer=$customerId
- GET
/invoices?customer=$customerId
- GET
/disputes?charge=$chargeId
- GET
/refunds?charge=$chargeId
Demo Video
Last Modified: 2024-12-11