Skip to main content

​
Pre-Built Tooling

CategoryDetails
AuthenticationAPI Key (Bearer Token)
Two-Way SyncYes
Events SupportedYes (extensive webhook events)
RealtimeYes (Webhooks)
Supports Rate LimitingYes (varies by request type)
Authentication Scopes SupportedN/A (API Key-based with restricted keys option)

​
Objects Supported

Alloy Automation supports syncing the following objects from Stripe:
  • Customers - Customer records and metadata
  • Charges - Payment charges
  • Payment Intents - Modern payment flows
  • Invoices - Invoices and line items
  • Subscriptions - Recurring billing subscriptions
  • Products & Prices - Product catalog and pricing
  • Payment Methods - Saved payment methods
  • Refunds - Refund transactions
  • Disputes - Chargebacks and disputes
  • Payouts - Transfers to bank accounts

​
Set Up Guide

​
Trial Access

QuestionAnswer
Offers free trial?Yes. Stripe is free to start with no setup fees. You only pay transaction fees when you process payments. Create free account
Requires paid sandboxNo. Test mode is available for free with unlimited test transactions.
Requires partnership to obtain authentication?No. Anyone can create a Stripe account and obtain API keys.

​
Authentication (API Key)

Stripe uses secret API keys for authentication via Bearer token.

​
Use Cases

​
1) Subscription management automation

Sync Stripe subscription data with CRM, billing, or customer success platforms to trigger onboarding workflows, usage tracking, and renewal reminders based on subscription events.

​
2) Revenue recognition and reporting

Extract payment, invoice, and payout data from Stripe to integrate with accounting systems, ERPs, or business intelligence tools for accurate financial reporting and reconciliation.

​
3) Customer lifecycle automation

Connect Stripe customer and payment data with marketing automation platforms to trigger targeted campaigns based on purchase behavior, subscription status, or payment failures.

​
4) Failed payment recovery

Automatically detect failed payments, subscription cancellations, or payment method updates in Stripe and trigger dunning workflows, customer notifications, or support ticket creation.

​
5) Multi-currency and international payments

Sync payment data across different currencies and payment methods from Stripe to centralized systems, enabling global financial reporting and compliance tracking.

​
API Gotchas

  • API Versioning: Stripe uses dated API versions (e.g., 2023-10-16). Your account is pinned to a specific version. To upgrade, test thoroughly in test mode, then upgrade your account version in the Dashboard. Stripe maintains backward compatibility but adds new features in newer versions.
  • Idempotency Keys: For POST requests that create objects (charges, customers, subscriptions), use idempotency keys (Idempotency-Key header) to safely retry requests without creating duplicates. Stripe stores idempotency keys for 24 hours.
  • Webhook Signature Verification: Always verify webhook signatures using the Stripe-Signature header and your webhook signing secret. This prevents malicious webhook events from reaching your system.
  • Pagination with starting_after: Stripe uses cursor-based pagination with the starting_after parameter. To paginate through results, use the id of the last object from the previous page as the starting_after value for the next request.
  • Expandable Properties: Stripe API responses often contain object IDs (e.g., customer: "cus_xxx"). Use the expand parameter to include full object details in a single request (e.g., expand[]=customer) instead of making separate API calls.
  • Rate Limiting: Stripe doesn’t publish specific rate limits but does throttle requests under extreme load. Implement exponential backoff for 429 responses. Most integrations won’t hit limits with normal usage patterns.
For questions or troubleshooting, contact support@runalloy.com.
⌘I