IntegrationStripe

Connect Stripe payments and subscriptions to Adrails

The Stripe connector adds payment and recurring revenue context for businesses whose conversion outcome lives outside a Shopify order. It reads charges, refunds and subscription records through a restricted key.

Reviewed Sep 22, 2026

Core capabilities

What enters the workspace and what stays controlled

Each source remains identifiable, permissions stay explicit and agents only receive the context the connector can support.

1

Connector capability

Connect campaign analysis to collected revenue

Stripe adds the payment outcome for SaaS, services and other businesses where store orders are not the relevant conversion record.

Charges
184
Refunds
$420
Subscriptions
72 active
2

Connector capability

Limit the key to read access

The connection uses a restricted API key with read access to charges and subscriptions.

Key
Restricted
MRR
Normalized
Writes
None
3

Connector capability

Keep payment data sourced

Payment records and advertising attribution answer different questions.

Collected
$16,840
MRR
$9,260
Net refunds
2.5%

Data flow

Payments and subscriptions become business outcomes

Charges, refunds and recurring records enter as restricted read data so collected revenue can inform paid acquisition decisions.

Stripe

Payment data

Charges
184
Refunds
$420
Subscriptions
72 active

Adrails sync

Restricted records

Key
Restricted
MRR
Normalized
Writes
None

Analysis

Revenue context

Collected
$16,840
MRR
$9,260
Net refunds
2.5%

Illustrative workspace data. Values demonstrate the connector flow and are not customer results.

FAQ

Common questions

Can Adrails refund a Stripe charge?

No. The connector has restricted read access and does not perform payment writes.

Which Stripe records are read?

The implemented streams cover charges, refunds and subscriptions.