See what the Stripe integration can do →
Introduction to Stripe
The Stripe integration on iPaaS.com turns an order or invoice owed on account in iPaaS.com into a Stripe invoice with a secure pay link, which Stripe emails to your customer, and brings each Stripe payment, refund and dispute back TO iPaaS.com on the same transaction. Paid Stripe subscription invoices arrive in iPaaS.com as orders with their customer, and Stripe customers are linked to your iPaaS.com customers by email.
API Version Support
The integration works with Stripe's REST API (its v1 endpoints at https://api.stripe.com), and makes every call with Stripe API version 2026-09-30.endive, whatever your Stripe account's default version is. It was tested against a Stripe account in test mode. See the Stripe Connections and Settings and Stripe API Endpoints articles for details.
Data Flows
The table below summarizes the data the integration can move between iPaaS.com and Stripe, and in which direction. Arrows show the direction of transfer:
→ iPaaS.com writes the data to Stripe
← iPaaS.com reads the data from Stripe
←→ the data can move in both directions
Allow Initialization? indicates whether that data can be bulk-loaded from Stripe when a subscription first connects. Whether a given flow is enabled, and in which direction, is configured per subscription during implementation.
iPaaS.com | Direction | Stripe | Allow Initialization? |
Transaction | ←→ | Invoice and sale | |
Customer | ←→ | Customer |
Orders and invoices owed on account go to Stripe as invoices with a pay link, and come back with their pay link, Stripe status and payments. Sales Stripe makes on its own (paid subscription invoices and Payment Link checkouts) arrive as orders with their lines, addresses and payments. Customers and their billing and shipping addresses move in both directions.
Versions and Release Notes
The integration follows its own version numbers. The current version is 1.0.0.
Version | Release Notes |
1.0.0 (current) | Initial release: Stripe invoices with a secure pay link for orders and invoices owed on account, kept in step as the transaction changes; payments, refunds and disputes brought back as payment lines; Stripe-made sales brought in as orders; customers linked by email in both directions; coded, searchable error messages. |
Features by Release
The capabilities below are grouped by the version in which they became available. For the current behavior and any limitations of a given feature, see the linked reference articles and the Stripe Integration Known Limitations article.
Version 1.0.0 (current) — Initial release
Invoices with a pay link (iPaaS.com to Stripe Invoice Mapping Documentation): an order or invoice owed on account becomes a Stripe invoice with every line, tax, shipping and discount, and Stripe emails it to the customer with a secure pay link.
Invoices kept in step (iPaaS.com to Stripe Invoice Mapping Documentation): a change before payment re-issues the invoice with a new pay link; a cancelled or deleted transaction voids its open invoice; a transaction paid in full another way closes its invoice as paid outside Stripe.
Payments, refunds and disputes (Stripe to iPaaS.com Invoice Mapping Documentation): the pay link, Stripe status and amount paid are written back onto the transaction, each payment arrives with Stripe's fee, and refunds and disputes are added as their own payment lines.
Sales Stripe makes (Stripe to iPaaS.com Sale Mapping Documentation): paid subscription invoices and Payment Link checkouts arrive as orders with their lines matched to your products, billing and shipping addresses, payments and customer.
Customers in both directions (Stripe to iPaaS.com Customer Mapping Documentation and iPaaS.com to Stripe Customer Mapping Documentation): Stripe customers are linked to your iPaaS.com customers by email before anything is added, and changes made in iPaaS.com reach the linked Stripe customer.
Webhooks set up for you (Stripe Installation Instructions): turning a Stripe event on registers the integration's own webhook endpoint in your Stripe account, with scheduled polls as a safety net.
Coded error messages (Stripe Error Messages): every error carries a stable code you can search on, with a plain-language cause and a resolution.
