New here? This page is a configuration reference for teams implementing the Stripe integration in iPaaS.com. It documents scope, design decisions, and settings to confirm before go-live. These are not product defects, and most items are handled during implementation by iPaaS.com or your Managed Integration Service Provider (MiSP). See Understanding Integration Scope & Known Limitations for how we document this for every integration.
These are the known limitations of the Stripe integration at the time this documentation was written. They come from the integration's design and from what Stripe's API allows, and they apply to all subscribers. Each one says what happens and what it means for you.
Platform Scope and Tested Versions
Built for: Stripe, through Stripe's API at
https://api.stripe.com.Stripe API version: every call is made with Stripe's API version 2026-09-30.endive, whatever your Stripe account's default version is, so a change to the account's default doesn't change how the integration behaves.
Tested: against a Stripe account in test mode with Stripe API version 2026-09-30.endive, in November 2026.
Stripe products used: Stripe Invoicing (the invoices and pay links), Stripe Payment Links and subscriptions (as the source of sales), customers, payments, refunds and disputes.
Not built for: Stripe Connect (acting on connected accounts), Stripe Terminal, setting up Stripe Tax (an invoice can ask Stripe Tax to calculate its tax, see item 10), Stripe Billing management (creating subscriptions, products or prices), or any payment platform other than Stripe. If Stripe launches a separate product line or a materially different API, this integration will not automatically support it.
1. Stripe charges its Invoicing fee on invoices paid through Stripe
Each pay link is a Stripe invoice, so invoices sent from iPaaS.com use Stripe Invoicing; there is no Payment Link or Checkout alternative. Stripe Invoicing has no fixed fee or setup cost. Stripe charges its Invoicing fee only when an invoice is fully or partly paid through Stripe, on top of its payment processing fees: 0.4% per paid invoice on Invoicing Starter and 0.5% on Invoicing Plus, with custom pricing for some businesses (Stripe: "Stripe Invoicing has no fixed fees or setup costs, but Stripe Payments pricing will apply." Stripe Invoicing pricing, read 2026-11-20). An invoice the integration marks paid outside Stripe (Close Stripe Invoices Paid Elsewhere) isn't charged the fee (Stripe: "If you mark the invoice as paid in the Dashboard, or pay it with the API and set paid_out_of_band to true, the Invoicing fee doesn't apply." Stripe Invoicing pricing FAQ, read 2026-11-20).
What this means for you: check which Invoicing plan and rates apply to your Stripe account before going live. Sales brought TO iPaaS.com from Payment Links and subscriptions add no Invoicing fee from the integration: any Stripe Billing or Payment Link fee on them comes from how those are set up in your Stripe account.
2. Payouts and fees stay in Stripe
Stripe payouts (the deposits to your bank) and balance transactions are not brought into iPaaS.com, because iPaaS.com has no data type for them.
What this means for you: each payment line carries its Stripe fee in the Stripe Fee custom field and its Stripe id in Stripe Payment ID. Use them to match payments in Stripe's own payout and balance reports.
3. A pay link is as visible as the system showing it
The pay link is written onto the iPaaS.com transaction in the Stripe Pay Link custom field. Whether your invoicing system can show that field to the customer depends on that system's own integration.
What this means for you: keep Stripe Emails Invoices set to Yes (the default), so Stripe emails each invoice with its pay link. If your own system emails invoices and can show the Stripe Pay Link field, you can set it to No and send the link yourself. Stripe keeps a pay link working until 30 days after the invoice's due date, or 30 days after it is issued when it has no due date, and never longer than 120 days (Stripe: "Invoice URLs expire 30 days after the due date. If the invoice doesn't have a due date, the invoice expires 30 days after it finalizes. In all cases, the expiration window is never longer than 120 days." Stripe Hosted Invoice Page, read 2026-11-20).
4. Payments made outside Stripe
A payment made outside Stripe before the invoice is issued (a deposit, for example) is shown on the Stripe invoice as a Payment already received line, so the invoice asks only for what is still owed. After the invoice is issued, the integration doesn't record a part payment made elsewhere on it: the invoice still asks for the amount it was issued for, and the warning STRP-BIZL-1006 is written to the transaction's Stripe Message. When the transaction is paid in full outside Stripe, the open Stripe invoice is marked paid outside Stripe, so the customer can't pay twice (setting Close Stripe Invoices Paid Elsewhere, default Yes; no money moves). With that setting at No, the invoice stays open and STRP-BIZL-1010 says so.
An order already paid in full when it reaches iPaaS.com (by card at checkout, for example) gets no Stripe invoice.
What this means for you:
For a part payment, tell the customer the amount still owed. Once the balance reaches 0, the invoice is closed as paid elsewhere.
The balance is read from the BalanceDue mapping, so set your on-account Payment Method there as well as in the filter (see Placeholder Values to Replace Before Go-Live).
To lower the issued invoice to the balance, issue a credit note on it in Stripe (Stripe's credit notes can record an amount credited outside Stripe). Don't void it in Stripe to get a new one: an invoice voided in Stripe isn't issued again (see item 24).
5. An invoice that Stripe has paid or credited stays as it is
Once a Stripe invoice has received a payment, or a credit note was issued on it in Stripe, later changes to its transaction are not sent to Stripe, and the warning STRP-BIZL-1003 is written to Stripe Message. A transaction cancelled in iPaaS.com after Stripe took its payment leaves the paid invoice as it is, and the warning STRP-BIZL-1004 is written to Stripe Message. An invoice marked uncollectible in Stripe is not changed, re-issued or voided from iPaaS.com either. Stripe locks an invoice once it is paid, and issuing a credited invoice again would bill the full amount again.
What this means for you: adjust the invoice in Stripe with a credit note or a refund. A refund made in Stripe arrives on the transaction as a negative payment line.
6. Changes after issue to the memo, customer name or phone
Stripe can't change most details of an invoice that is already finalized, including the memo, customer name and phone (Stripe API reference, update an invoice: "Once an invoice is finalized, you can no longer change most of its details"). The template maps the customer name; the memo and phone apply only if you map them. A change to one of these in iPaaS.com after the invoice is issued doesn't reach the issued invoice; the transaction's Stripe Message shows STRP-BIZL-1018 naming the fields that changed, until they match the invoice again or a new invoice is issued. A change to the lines or the total does: the invoice is voided and issued again (item 8).
What this means for you: check these fields before the transaction is first sent. To issue an invoice that shows a corrected name, memo or phone before it is paid: for a name or phone, update the customer in Stripe first (an invoice takes the name and phone from its Stripe customer); then void the invoice in Stripe, clear the transaction's Stripe Invoice ID custom field and save it, and a new invoice is issued (item 24).
7. A change that fails a check leaves the old invoice open
When a transaction that already has an open Stripe invoice is changed and the change fails a check (for example STRP-VALD-1006, STRP-VALD-1010 or STRP-VALD-1011), or its Stripe customer can't be told apart from another (STRP-BIZL-1012), nothing is sent: the invoice already issued stays open, and payable, at its old amount. The integration checks the whole transaction before it changes anything in Stripe. A transaction whose total drops to 0 is the exception: its invoice is taken out of use.
What this means for you: correct the transaction and send it again. If the old invoice must not be paid meanwhile, cancel the transaction in iPaaS.com (its open invoice is voided) or void the invoice in Stripe.
8. A changed transaction gets a new invoice and a new link
Stripe locks a finalized invoice's amounts. When a transaction changes before any payment, its Stripe invoice is voided and a new one is issued with -R1 added to the number (then -R2 and so on), with a new pay link. A cancelled transaction's open invoice is voided and its link cleared, and a deleted one's is voided through Delete Stripe Invoice FROM iPaaS.com. A transaction sent again with nothing changed sends nothing to Stripe.
What this means for you: the new link replaces the old one on the transaction, and Stripe emails the new invoice when Stripe Emails Invoices is Yes. A customer who opens an old link sees a voided invoice.
9. Transaction numbers have at most 22 characters
The transaction number becomes the Stripe invoice number the customer sees. Stripe allows invoice numbers of up to 26 characters (Stripe API reference, create an invoice: number, maximum length 26), and the integration keeps 4 for the re-issue suffix (-R1), so a longer number is refused (STRP-VALD-1005). Stripe refuses an invoice number already used by another invoice in the account ("number is already used by another invoice").
What this means for you: keep transaction numbers to 22 characters, or map a shorter value to TransactionNumber, and keep them unique across every system that bills through the same Stripe account: a number already used is refused by Stripe (STRP-EXTN-1004, quoting Stripe).
10. The invoice total is the transaction's total
The Stripe invoice is built from the transaction's lines plus a Tax line, a Shipping line and a negative Discount line. Their sum must equal the transaction's Total, or nothing is sent (STRP-VALD-1006). A Stripe customer with a credit balance in the invoice's currency, which Stripe would take off the invoice, is refused before any invoice is made (STRP-BIZL-1015, naming the customer and the balance), and nothing is made until the balance is cleared. If Stripe still finalizes an invoice for a different amount, the integration voids it at once (STRP-BIZL-1005, naming both amounts), so the customer is never asked for a wrong amount.
You can instead have Stripe calculate the tax or take discounts off, on the transaction or its lines: map TaxRateIds to your Stripe tax rates, AutomaticTax to have Stripe Tax calculate it, or DiscountCodes to your Stripe coupons or promotion codes. AutomaticTax needs Stripe Tax set up in your Stripe account and a Stripe customer whose address Stripe Tax can place. The transaction's own TaxAmount or DiscountAmount must then carry no amount (STRP-VALD-1006), and the invoice Stripe calculates must still come to the transaction's Total: if it doesn't, it is voided before it is emailed (STRP-BIZL-1017, naming both amounts). A retry of the unchanged transaction gives the same error without making another Stripe invoice for 24 hours after the void; after that, one retry asks Stripe again, so a fix made only in Stripe's tax settings is picked up.
What this means for you: map each line's price after its line discount, and the tax, shipping and order discount. If you use Stripe's tax or discounts instead, make sure the Total your system sends is what Stripe will calculate, and dismiss a STRP-BIZL-1017 error once you have corrected it. Clear a customer's credit balance in Stripe if it would reduce an invoice.
11. Every invoice and customer sent to Stripe needs an email
The integration finds or creates the Stripe customer by email, and Stripe emails the invoice there. A transaction or customer without a valid email is refused before anything reaches Stripe (STRP-VALD-1004).
What this means for you: make sure your systems send the customer's email with each invoice on account and each customer.
12. Sale lines must match your products
Sales Stripe made arrive as orders, and iPaaS.com refuses the whole sale when a line's SKU isn't one of your products or variants (iPaaS.com's NFND-1003, naming the SKU sent). Stripe's own product ids are not your SKUs. The Sku mapping of Add/Update Stripe Sale Line TO iPaaS.com must stay: without it every sale is refused, and the error doesn't name the field.
What this means for you: set a lookup key on each Stripe price, or sku metadata on each Stripe product, equal to the iPaaS.com SKU. Anything else takes the Sku mapping's fallback, which you set to one of your products (see Placeholder Values to Replace Before Go-Live).
13. A sale's customer is set when the sale is created
iPaaS.com sets a transaction's customer only when it creates the transaction. Before a Stripe-made sale is created, the integration brings its Stripe customer into iPaaS.com through Add/Update Stripe Customer TO iPaaS.com. When that customer can't be brought in (no email, no name or company, or an email already used by an iPaaS.com customer linked to another Stripe customer), or when the sale has no Stripe customer (a Payment Link left at Stripe's default customer setting, which creates a customer only when one is required, makes none for a one-time payment), the sale is still created with the buyer's email, and iPaaS.com sets the customer whose email matches, when there is one; otherwise it has no customer.
What this means for you: keep Add/Update Stripe Customer TO iPaaS.com turned on and make sure Stripe customers have an email. A sale created without its customer is corrected by deleting the order in iPaaS.com and syncing the sale again with its Stripe id once the customer is in iPaaS.com.
14. One email, one customer
iPaaS.com allows one customer per email, and the integration doesn't merge Stripe customers. A Stripe customer arriving TO iPaaS.com is linked to the iPaaS.com customer it was created for, else to the one iPaaS.com customer with the same email. A second Stripe customer with that email can't be linked to the same iPaaS.com customer: it is refused with STRP-BIZL-1009, and so is one whose email several iPaaS.com customers share. Sending FROM iPaaS.com, two or more Stripe customers with the email and none linked to the iPaaS.com customer can't be told apart, and nothing is sent (STRP-BIZL-1012, naming them).
What this means for you: merge the customers in Stripe, or give one its own email; if several iPaaS.com customers share the email, merge them in iPaaS.com first. Then resync.
15. Payments reach your ERP only through a compatible ERP integration
Stripe payments land on the iPaaS.com transaction as payment lines. They reach your ERP or invoicing system only when that system's integration has workflows compatible with this integration's: it must take a payment added to a transaction it already has, because a Stripe payment usually arrives after the order or invoice was sent. Many ERP integrations don't. Some take payments only when the order or invoice is first sent, some take no payments at all, and some post an on-account payment line as if it were paid. Turning on that subscription's outbound transaction update event, or sending the transaction again with Manual Sync, re-sends the transaction but doesn't make an incompatible integration compatible. At the time this documentation was written, end-to-end tests with several ERP integrations found one with compatible workflows.
What this means for you: before relying on Stripe payments reaching your ERP, check that your ERP integration's workflows are compatible, and prove one payment end to end in a staging subscription. Otherwise the payments and Stripe Invoice Status stay on the iPaaS.com transaction.
16. One system bills each Stripe invoice
If another app already syncs invoices between your ERP and Stripe (Stripe's own, for example), both would issue Stripe invoices for the same bills.
What this means for you: choose one system for each kind of invoice. If another system marks its own Stripe invoices, subscriptions or checkouts with a metadata key, name that key in Skip Objects Marked In Metadata and those objects are never brought in. Set Bring In Subscription Invoices to No when your Stripe subscriptions already reach your ERP another way.
17. One subscription and one invoice collection per set of invoices
Each subscription issues its own Stripe invoices, and the first subscription to issue an invoice for a transaction owns it. A transaction already linked to a Stripe invoice passes every Add/Update Stripe Invoice FROM iPaaS.com filter, so two such collections on one subscription would both act on the same transactions.
What this means for you: give each subscription a filter that doesn't overlap another subscription's, and keep exactly one Add/Update Stripe Invoice FROM iPaaS.com collection on a subscription. To cover more transactions, widen its filter rather than copying the collection. If a transaction ever has two open Stripe invoices, nothing is sent and STRP-BIZL-1013 names both: void the unwanted one in Stripe, then send the transaction again.
18. Webhook endpoints: up to 16 per Stripe account
Each subscription registers its own webhook endpoint in your Stripe account when you turn on its first Stripe event, and Stripe allows up to 16 event destinations per account (Stripe: "You can register up to 16 event destinations with Stripe", https://docs.stripe.com/webhooks, read 2026-11-18). A subscription that would be the 17th on the same Stripe account can't register one, and turning its event on gives STRP-EXTN-1005.
Turning the last event off deletes the subscription's endpoint. Turning an event on again registers a new one, also after the Secret Key has changed.
What this means for you: plan at most 16 subscriptions with webhooks per Stripe account, including any other software's webhook endpoints. A subscription without an endpoint still receives changes through its poll events (item 22).
19. Which Stripe sales come in
Three settings decide which Stripe-made sales arrive as orders: Bring In Subscription Invoices (default Yes), Bring In Payment Link Sales (default Yes) and Bring In Other Invoices (default No; invoices made in the Stripe Dashboard or by another system, once paid). Checkout Sessions created by another system's code (an online store using Stripe's hosted checkout, for example) and payments with no invoice or Checkout Session are not brought in: that system sends its own orders.
What this means for you: set each Bring In setting to match where your Stripe sales already go. The settings decide only which new sales arrive: a sale already in iPaaS.com keeps receiving its refunds and disputes.
20. Payment lines are added, never changed
Systems that post payments to their books need posted amounts to stay as they are. Each Stripe payment lands as its own payment line, and a refund or dispute adds a negative line; a refund that failed or a dispute won adds a positive reversal. An amount once posted never changes. The status of each line is worked out from Stripe's own status:
A payment: Paid (succeeded), Pending (processing, such as a bank debit on an invoice), Authorized (not captured yet) or Failed (failed). A sale made in Stripe arrives only once its payment has succeeded or been authorized, so it never arrives with a Pending or Failed payment. An authorization released in Stripe turns the payment Failed.
A refund: Refunded, or Pending while Stripe is still processing it; a refund that failed adds a RefundReversed line.
A dispute: Disputed while it is open (Stripe's needs response, under review or prevented), then Won or Lost; money returned after a dispute adds a Reinstated line. An inquiry that holds no money adds nothing.
What this means for you:
A system that adds up payments should count Paid lines and the negative and positive lines, not Pending, Failed or Authorized. Stripe Amount Paid on the transaction does this for you.
iPaaS.com stores a payment's status as text. To use your own status names, change the payment Status mapping to a Lookup Translation with a row for every value above; a value with no row is saved with an empty status.
Every payment uses the one Payment Method named in the payment collections, whatever the customer paid with.
21. The transaction's own status and its Stripe status
The transaction belongs to the system that sent it. Stripe Invoice Status says where Stripe stands (Draft, Open, PartiallyPaid, Paid, PartiallyRefunded, Refunded, PaidWithCredit, Disputed (a dispute is open or was lost), Void or Uncollectible), while the transaction's own Status changes only to Complete when the invoice is paid in full; Cancelled stays Cancelled. A refund doesn't change the transaction's status. A new Stripe-made sale arrives Complete and keeps the status your systems give it.
What this means for you: read Stripe Invoice Status and Stripe Amount Paid for the Stripe side of each transaction, including refunds and disputes.
22. Webhooks and poll events
Stripe reports changes through the webhook endpoint the integration registers for the subscription when you turn on Stripe events under Inbound Data Flows. Two poll events catch anything a webhook missed, and they are not created for you. Stripe keeps events for 30 days (Stripe API reference, list all events: "going back up to 30 days"), so a poll that hasn't run for longer can't read the gap, and the warning STRP-BIZL-1002 asks for a resync. A poll's first run looks back one hour (validate this in a staging subscription before relying on it in production). When Stripe sends many events for one invoice at the same moment (a dispute can bring five or more), at the time this documentation was written one of those transfers can fail with iPaaS.com's own error "External Id must be unique" (BIZL-1003); the others complete, the transaction ends up right, and the failed one is retried.
What this means for you: turn on the Stripe events you need; nothing is set up in Stripe by hand. Create scheduled iPaaS.com Events for invoice.poll and customer.poll, for example every 15 minutes. After a long gap, resync the transactions and customers changed during it. A BIZL-1003 error left after a burst of events for an invoice can be dismissed once the transaction shows the payment, refund or dispute.
23. Records move from the day the integration is set up
Only changes made after the webhooks or the poll start arrive. Stripe customers and sales made before the integration was set up don't come TO iPaaS.com by themselves, and transactions already open in iPaaS.com get no Stripe invoice until they change. The integration has no bulk initialization.
What this means for you: use Manual Sync for the records that should move: TO iPaaS.com with the Stripe id (cus_ for a customer, in_ or cs_ for a sale), or FROM iPaaS.com with the transaction id for an open invoice on account.
24. An invoice voided in Stripe isn't issued again
A void made in Stripe (in the Stripe Dashboard, for example) is treated as a decision made in Stripe: the integration doesn't issue the invoice again when the transaction changes, and Stripe Message shows STRP-BIZL-1014. Voids the integration makes itself (a re-issue or a cancel) are not affected.
What this means for you: to bill the transaction again, clear its Stripe Invoice ID custom field and save it: a new Stripe invoice is issued. To stop billing it, cancel the transaction.
25. Customers sent to Stripe
By default, Add/Update Stripe Customer FROM iPaaS.com sends only customers already linked to Stripe (their Stripe Customer ID custom field has a value), because invoices find or create their own Stripe customer and sending every customer would fill your Stripe account with people who don't pay through it. Each update sends only the fields that changed in iPaaS.com since the last send, so an edit made in Stripe stays until the same field changes in iPaaS.com. A value blanked in iPaaS.com is cleared in Stripe on the next update, but only when the integration sent that field before: a field that was always blank in iPaaS.com, or a Stripe customer the integration has never written, clears nothing, so a value typed in Stripe stays. Balance, InvoicePrefix, NextInvoiceSequence and the payment fields are never cleared, and a blanked TaxExempt goes back to none. A country that isn't a two-letter code (for example USA) is refused with STRP-VALD-1012 and nothing is sent. Stripe customers are never deleted from iPaaS.com: a deleted Stripe customer loses its invoices and payment history.
Stripe keeps no phone on a customer's billing address, so the integration sends the billing phone as the customer's phone, or keeps it in the Stripe customer's metadata when the customer has a different phone of its own, and brings it back from there TO iPaaS.com.
What this means for you: choose which customers are sent (see Placeholder Values to Replace Before Go-Live), keep Add/Update Stripe Customer TO iPaaS.com turned on (it writes Stripe Customer ID), and store countries as two-letter codes (or add a translation on the address Country mapping that turns country names into codes). Manage Stripe customers you no longer need in Stripe.
26. Transactions and customers only
The integration handles transactions (with lines, addresses and payments) and customers (with addresses). Any other mapping collection is refused with STRP-BIZL-1007, and a line, address or payment collection added on its own is refused with STRP-BIZL-1011: those records move only with their transaction or customer. Products are matched by SKU, not synced.
What this means for you: keep only the Stripe template collections on the subscription.
27. Currency
The default Add/Update Stripe Invoice FROM iPaaS.com collection maps no currency, so every invoice is issued in your Stripe account's default currency, even for a Stripe customer billed in another currency before.
What this means for you: if you bill in another currency, map Currency (a three-letter code) in that collection.
28. Keys: live keys only in production
A live key (sk_live_ or rk_live_) is refused outside iPaaS.com production (STRP-AUTH-1004), because live keys charge real cards. A publishable key (pk_) is refused (STRP-AUTH-1003). A restricted key works when it has the permissions listed in Stripe Installation Instructions; when Stripe refuses a call, STRP-AUTZ-1001 names it.
What this means for you: use a test-mode key on staging and test subscriptions, and make sure the production subscription holds your live key before going live: a test key on production issues invoices in Stripe's test mode, where no customer can pay them. When a key is refused, each transfer shows "Unable to connect to subscription" in Dashboard / Integration Monitoring / Error Logs; the coded reason is written to iPaaS.com's company log rather than the error list, and the causes are listed in Stripe Error Messages.
29. Removing a mapping from a TO iPaaS.com collection
An update FROM Stripe replaces the whole iPaaS.com record, so a field whose mapping you removed is written empty: a payment line without its Amount mapping lands as 0.00 with no error, and a customer address without its Address1 mapping loses its street on every update. A sale line without its Sku mapping is refused as a whole (item 12). The templates map every iPaaS.com field Stripe doesn't own with a formula that returns the value already on the record (for example the transaction's created and updated dates, a sale line's QtyShipped, an address's Type), so nothing your systems set is cleared while the mappings stay as shipped.
What this means for you: keep every mapping. To stop Stripe from changing a field, replace its mapping with a Dynamic Formula that returns the record's current value instead of removing it, for example return DestinationValue != null ? (object)DestinationValue.TransactionCreatedDateTime : null;.
30. Handled in Stripe
Charging, refunding or voiding a payment FROM iPaaS.com: money moves only in Stripe.
Credit notes FROM iPaaS.com.
Deleting a Stripe customer FROM iPaaS.com.
Payouts and balance transactions.
A product catalog sync to or from Stripe.
A pay link without Stripe Invoicing.
Recording a part payment made outside Stripe on an invoice already issued.
Creating Stripe subscriptions, products or prices FROM iPaaS.com.
Sending card or bank details to Stripe: customers pay on Stripe's own page.
Bringing card numbers, card expiry dates, card fingerprints or Stripe's payment secrets (client secrets) into iPaaS.com: the template brings the card's brand and last four digits, and its funding type, country, network and wallet can be mapped.
Deleting the iPaaS.com customer when its Stripe customer is deleted, or the Stripe customer when its transaction is deleted.
What this means for you: handle these in Stripe. If your workflow needs one of them from iPaaS.com, submit a feature request through your iPaaS.com partner channel describing it; requests like this inform future releases.
31. Outcomes that log no error
These situations are expected. Nothing is written to the error list for them, and nothing needs fixing.
A transaction that the Add/Update Stripe Invoice FROM iPaaS.com filter doesn't pass (for example an order already paid at checkout, or one that isn't on your on-account payment method): nothing is sent, and no error appears. Until the filter's on-account placeholder holds your on-account payment method's name (and the same name is in the BalanceDue mapping), nothing is invoiced at all, with no error.
A transaction whose Stripe invoice was not issued by this subscription for it (a sale Stripe made, or another subscription's invoice): sending it FROM iPaaS.com changes nothing in Stripe.
A transaction sent again with nothing changed: nothing is sent to Stripe.
A declined card attempt on a Stripe invoice: nothing is added, and the invoice stays open with the same pay link so the customer can try again.
A Stripe sale the integration doesn't bring in: one switched off by the Bring In Payment Link Sales, Bring In Subscription Invoices or Bring In Other Invoices setting, one carrying the key named in Skip Objects Marked In Metadata, an invoice not yet paid, a Checkout Session created by another system, or a payment with no Stripe invoice or Checkout Session. Nothing is transferred.
A Stripe invoice issued by another iPaaS.com subscription: this subscription leaves it alone.
A notification for something that doesn't exist in your Stripe account: the integration reads every record again from Stripe with your key, so nothing is transferred.
What this means for you: when a record you expected doesn't move and no error appears, check these first, then the collection's filter.
Placeholder Values to Replace Before Go-Live
The templates ship these values for you to set. Each is also described where it appears in the mapping documentation.
Add/Update Stripe Invoice FROM iPaaS.com: the on-account Payment Method (filter and BalanceDue mapping), and which customers to bill.
Add/Update Stripe Invoice Payment TO iPaaS.com and Add/Update Stripe Sale Payment TO iPaaS.com: the Payment Method.
Add/Update Stripe Sale Line TO iPaaS.com: the fallback SKU.
Add/Update Stripe Customer FROM iPaaS.com: which customers to send.
Defaults in Add/Update Stripe Invoice FROM iPaaS.com
On-account Payment Method (filter and BalanceDue, Dynamic Formula)
Collection: Add/Update Stripe Invoice FROM iPaaS.com
Shipped default:
var onAccountMethod = "REPLACE with your on-account payment method";in the filter and in the BalanceDue mapping.Why it's a placeholder: the template can't know the name of your on-account (pay later) Payment Method. Until the filter is set nothing is invoiced; until BalanceDue is set an invoice asks for the whole total and nothing is closed as paid elsewhere.
Suggested action: put your Payment Method's name, exactly as in iPaaS.com (for example A/R), in both places.
Defaults in the payment collections
Method (Static)
Collection: Add/Update Stripe Invoice Payment TO iPaaS.com and Add/Update Stripe Sale Payment TO iPaaS.com
Shipped default:
REPLACE with your iPaaS.com card Payment Method nameWhy it's a placeholder: every payment line needs a Payment Method that exists in iPaaS.com; until it is set, the transfer is refused (VALD-1036): a Stripe payment doesn't update its invoice's transaction, and a sale made in Stripe isn't created.
Suggested action: set it to the Payment Method you use for Stripe payments (for example Credit Card) on both collections.
Defaults in Add/Update Stripe Sale Line TO iPaaS.com
Sku fallback (Dynamic Formula)
Collection: Add/Update Stripe Sale Line TO iPaaS.com
Shipped default:
REPLACE with your SKU for Stripe items not in your catalogWhy it's a placeholder: a sale line that matches none of your products takes this SKU; until it is a real product, such a sale is refused (NFND-1003).
Suggested action: set it to the SKU of a product you keep for Stripe items not in your catalog (for example MISC-STRIPE-SALE).
Defaults in Add/Update Stripe Customer FROM iPaaS.com
Which customers are sent (filter)
Collection: Add/Update Stripe Customer FROM iPaaS.com
Shipped default: linked customers only:
return ("" + GetCustomFieldValue(CustomFields, "Stripe Customer ID")).Length > 0;Why it's a placeholder: whether Stripe should hold only customers that came from Stripe or every iPaaS.com customer with an email is your choice.
Suggested action: keep it, or replace the last line with
return !string.IsNullOrEmpty(EmailAddress);to send every customer with an email.
Also review the settings Stripe Emails Invoices (Yes), Invoice Days Until Due (30), Close Stripe Invoices Paid Elsewhere (Yes), Bring In Subscription Invoices (Yes), Bring In Payment Link Sales (Yes), Bring In Other Invoices (No) and Skip Objects Marked In Metadata (blank) in Stripe Connections and Settings, and create the Stripe custom fields with exactly the names in Stripe Installation Instructions: the filters read Stripe Invoice ID and Stripe Customer ID by name.
This page covers 30 limitations. For the full detail of each collection, see the mapping documentation listed below.
