Stripe
Configuration guide for the Stripe connector in Recurly Engage—activation, data sync, 1-Click actions, and subscription management.
Prerequisites
- You must have Company or App Administrator permissions in Recurly Engage.
- You must have a Stripe account with API access credentials and webhook capability.
Limitations
- Users in Recurly Engage must have
stripe_idoremail_addresstraits for action targeting and webhook syncing.
Definition
Key benefits
Key details
Activation
You can activate the Stripe connector using one of two methods: Stripe Connect or an API key. Stripe Connect integrates with Recurly Engage by authenticating with an existing Stripe user account. Alternatively, you can generate a new API key.
Option 1: Stripe Connect

Option 2: API key

| Resource type | Permissions | Connect permissions |
| Customers | Write | None |
| Subscriptions | Write | None |
| Products | Read | None |
| Prices | Read | None |
| Coupons | Read | None |
| Promotion Codes | Read | None |
Data integration
1-Click actions
After activation, available plans and coupons sync periodically for use in prompts. Make sure each user record includes stripe_id or email_address.
Automated data sync
When you use Stripe Connect, Recurly Engage creates a webhook to sync subscription events in real time. The imported traits include:
| Trait name | Values |
subscription_status | incomplete, incomplete_expired, trialing, active, past_due, canceled, unpaid, paused or NONE |
delinquent | true, false (set to true when a payment fails) |
current_period_start | <Start date of current billing period> |
current_period_end | <End date of current billing period> |
canceled_at | <Date of cancellation> |
cancel_at_period_end | true, false |
trial_start | <Start date of trial> |
trial_end | <End date of trial> |
subscription_plan | <Name of current or most recent subscription plan> |
recurring_interval | day, week, month, year |
coupon | <Coupon name> |
payment_card_brand | <card brand> (for example, visa, mastercard, amex, unknown) |
payment_card_country | <country code> (two-character ISO) |
payment_card_expiration | <Payment card expiration date> |
payment_card_wallet_type | <wallet type> (for example, apple_pay, google_pay, etc.) |
Supported actions
Attach these 1-Click actions to prompt interactions once your data sync is active:
| Action | Description | User dependencies | Additional instructions |
| Update existing subscription | Switch user to a different product | stripe_id or email_address | Multiple proration options are available. See the Stripe Proration Guide. |
Additional resources
Updated 14 days ago