Skip to main content

Integration with Stripe (Coming Back Soon)

Sarunas avatar
Written by Sarunas
Updated yesterday

Stripe is a payments infrastructure platform enabling businesses to accept credit cards, handle subscriptions, issue refunds, and manage financial flows. Integrating Stripe with Omnisend allows you to leverage payment events (e.g., purchase completed, subscription started, refund issued) to drive more targeted marketing, segmentation, and automation.

Key Benefits

  • Automatically add customers who make payments or start subscriptions in Stripe into Omnisend as contacts.

  • Trigger email/SMS flows based on Stripe events (e.g., “payment succeeded”, “subscription canceled”).

  • Keep contacts in sync (update contact info from Stripe).

  • Recover failed payments with targeted messaging.

Setup Process

Step 1. Go to the Omnisend App Market and find Stripe. Click the 'Connect now' button.

Step 2. Wait a moment for the page to load, then decide if you want all available events to be passed to Omnisend and click 'Continue'.

Step 3. Click on the 'Grant Access' button below Stripe.

You will need to enter your Secret Key in this step. To find it – go to your Stripe account, go to Developers → API keys, and click Reveal live key or Create secret key, then paste it in this step.

Once done, click 'OK, thank you' and 'Continue'.

Lastly, click 'Start' and 'Confirm'.

That's all! You can come back and enable or disable different events from being captured, or pause everything altogether.

What Data is Passed

Stripe - Payment succeeded

Field

Description

amount

Amount paid

reason

Payment reason

status

Payment status

invoice

Invoice ID

statement

Statement text

invoice_url

Invoice URL

attempt_count

Number of attempts

next_retry_at

Next retry date

payment_last4

Last 4 digits of the card

payment_method_type

Payment method type

Stripe - Canceled subscription

Field

Description

status

Subscription status

currency

Currency

stripe_customer_id

Customer ID

most_recent_invoice

Most recent invoice ID

stripe_subscription_id

Subscription ID

end_of_subscription_date

End of subscription date

Stripe - New refund

Field

Description

last4

Last four digits of the card

status

Refund status

invoice

Invoice ID

currency

Currency

invoice_url

Invoice URL

amount_refunded

Amount refunded

payment_method_type

Payment method type

Stripe - Payment failed

Field

Description

last4

Last four digits of the card

reason

Failure reason

status

Payment status

invoice

Invoice ID

currency

Currency

amount_due

Amount due

invoice_url

Invoice URL

payment_method_type

Payment method type

attempt_count

Number of attempts

next_retry_at

Next retry date

Stripe - New charge

Field

Description

last4

Last four digits of the card

amount

Charge amount

object

Object type

currency

Currency

charge_id

Charge ID

payment_method_type

Payment method type

New subscription

Field

Description

status

Subscription status

currency

Currency

first_invoice

First invoice date

stripe_customer_id

Customer ID

stripe_subscription_id

Subscription ID

Stripe - New payment

Field

Description

object

Object type

status

Payment status

invoice

Invoice ID

currency

Currency

created_at

Created at

capture_method

Capture method

amount_in_cents

Amount in cents

received_amount_in_cents

Received amount in cents


Stripe - New invoice

Field

Desciption

status

Invoice status

invoice

Invoice ID

currency

Currency

amount_due

Amount due

invoice_url

Invoice URL

attempt_count

Number of attempts

next_retry_at

Next retry date

amount_in_cents

Amount in cents

subscription_id

Subscription ID

Contact created

Field

Description

First Name

Customer first name

Email

Customer email

Phone

Customer phone

Use in Automations

Once the data flows into Omnisend, here are ways you can use it:

  • Welcome or Thank You series — trigger immediately after a “payment succeeded” event

  • Subscription lifecycle flows — trigger based on subscription start or cancellation

  • Win‑back / recovery flows — trigger if a refund or failed payment event occurs

Additional Notes

  • Historical Stripe data (older sales before setup) will not be synced

  • Rate limits or API quotas of Stripe or the integration may apply

If you didn’t find the answer to your question, reach out to our support team through the in‑app chat or at [email protected]. Our team is available 24/7.

Did this answer your question?