These steps are for the person who sets up a company's Stripe connection in iPaaS.com: the company's own administrator, or their Managed Integration Service Provider (MiSP). Set it up twice: first on a test subscription with a Stripe test key (see Test with a Test Key First), then on your live subscription. Each time, do the settings and template values first, and turn on the data flows and poll events last, because they start real work.
Before You Begin
Before you can install the Stripe subscription, you need:
A Stripe account, and a Stripe user who can create API keys (an administrator, or a user allowed to open Developers > API keys). The integration issues Stripe invoices: Stripe Invoicing has no fixed or setup fee, and Stripe charges its Invoicing fee on each invoice paid through Stripe; see Stripe Integration Known Limitations.
An iPaaS.com user who can manage subscriptions in your company: add a subscription, edit its settings and mappings, and create events.
A system connected to iPaaS.com that sends the orders or invoices to be paid, with the customer's email and an on-account (pay later) payment on each.
A Payment Method in iPaaS.com to record Stripe payments with.
For sales Stripe makes: a lookup key on each Stripe price, or sku metadata on each Stripe product, set to the matching iPaaS.com SKU.
One Stripe key, as described below. No OAuth application or redirect address is needed.
The integration needs either your account's secret key (it starts sk_) or a restricted key (it starts rk_) that can do only what the integration needs. Use a test-mode key on a test subscription and a live-mode key only on your live subscription.
To use the secret key: in the Stripe Dashboard, open Developers > API keys, reveal the Secret key, and paste it straight into Secret Key on the subscription.
To create a restricted key:
Open the iPaaS.com subscription's settings in another browser tab first: Stripe shows a new key only once.
Sign in to the Stripe Dashboard at https://dashboard.stripe.com. For a test subscription, switch to test mode (or your test sandbox) first.
Open Developers > API keys and choose Create restricted key. If Stripe asks how you will use the key, choose the option that lets you set each permission yourself.
Name it so nobody deletes it by mistake, for example iPaaS.com.
Set these permissions and leave every other one at None:
Dashboard section | Permission | Level |
Core | Customers | Write |
Core | Charges and Refunds | Read |
Core | Balance | Read |
Core | Payment Disputes | Read |
Core | Payment Intents | Read |
Core | Products | Read |
Core | Events | Read |
Billing | Invoices | Write |
Billing | Prices | Read |
Checkout Sessions | Checkout Sessions | Read |
Connect | Accounts | Read |
Webhook Endpoints | Webhook Endpoints, Event Destinations | Write |
Create the key. A test key starts rk_test_ and a live key rk_live_; if you meant to make a test key and it starts rk_live_, delete it and start again in test mode.
Copy the key and paste it straight into Secret Key on the subscription. Don't send it by email or chat. If your MiSP is doing the setup, paste the key in yourself.
If a permission is missing later, the transfer fails with STRP-AUTZ-1001, naming the refused call. You can edit a restricted key's permissions at any time under Developers > API keys.
Installation Instructions for Integration Setup
Go to Subscriptions and click Search Certified Integration Marketplace and Subscribe.
Click the Stripe integration tile.
Click the Subscribe button.
Enter the name of the subscription and select a version. It can be any relevant and unique subscription name within the company.
Format: [Product Name] - [Environment/Purpose]
Example: Stripe – Release
Select Create Default Mappings (recommended). If you don't want to create default mappings and want to create all mappings yourself, un-check this box.
API Url: keep the default,
https://api.stripe.com. Only an https address on Stripe's API host is accepted.Secret Key: paste your Stripe secret key or restricted key. It is stored encrypted, and the integration masks keys in its own messages.
Stripe Emails Invoices: Yes (the default) to have Stripe email each new invoice, with its pay link, to the customer; No to send the link yourself. Stripe sends no invoice emails from a test key.
Invoice Days Until Due: the days from issue until an invoice is due when no due date is mapped, from 1 to 365 (default 30).
Close Stripe Invoices Paid Elsewhere: Yes (the default) to mark an open Stripe invoice paid outside Stripe when the transaction is paid in full another way, so the customer can't pay twice. No money moves.
Bring In Payment Link Sales, Bring In Subscription Invoices and Bring In Other Invoices: choose which Stripe-made sales arrive in iPaaS.com as orders (defaults Yes, Yes and No).
Skip Objects Marked In Metadata: leave blank, or enter a Stripe metadata key that another system writes on its own invoices or checkouts, so those sales aren't brought in twice.
Leave the throttle and concurrency fields at the values they are pre-populated with, unless your MiSP advises otherwise:
API Throttle Limit: how many calls the integration makes to Stripe in each throttle window. Default Value: 500. Recommended: 5 for the initial load, 500 for ongoing and high-volume use.
API Throttle Seconds: the length of that window. Default Value: 60 seconds.
API Throttle Limit (To iPaaS): how many calls the integration makes to iPaaS.com in each window. Default Value: 500.
API Throttle Seconds (To iPaaS): the length of that window. Default Value: 60 seconds.
Concurrent Connections: how many calls to Stripe can run at the same time. Default Value: 2. Lower it if
STRP-EXTN-1003(Stripe's rate limit) appears often.Concurrent Batch Executions: how many batches can run at the same time. Default Value: 10.
Click Apply to save the settings.
Every setting is described in Stripe Connections and Settings. A value a setting doesn't allow stops the connection with STRP-BIZL-1001 naming the setting. A live key (sk_live_ or rk_live_) is refused outside iPaaS.com production (STRP-AUTH-1004), and a publishable key (pk_) is always refused (STRP-AUTH-1003). A test key isn't refused on a live subscription, so make sure your live subscription holds the live key before you go live.
Create the Custom Fields
The templates write these iPaaS.com custom fields. Create any your company doesn't have yet, with exactly the name shown, before you turn anything on. If a field with the same name but another purpose already exists, ask your iPaaS.com contact first: other integrations may use it.
Custom field | On | Holds |
Stripe Invoice ID | Transaction | The Stripe invoice issued for the transaction, or a sale's Stripe invoice. Two filters read it. |
Stripe Pay Link | Transaction | The page where the customer pays. |
Stripe Invoice Status | Transaction | The invoice's state in Stripe. |
Stripe Amount Paid | Transaction | The money Stripe received, less refunds and disputes. |
Stripe Message | Transaction | Anything to act on in Stripe; blank when there is nothing. |
Stripe Checkout Session ID | Transaction | A Payment Link sale's Checkout Session. |
Stripe Payment ID | Transaction Payment | The Stripe payment, refund or dispute behind the payment line. |
Stripe Fee | Transaction Payment | Stripe's processing fee, or the dispute fee. |
Stripe Customer ID | Customer | The linked Stripe customer. The Customer FROM iPaaS.com filter reads it. |
Set the Template Values
A new subscription gets these mapping collections, with no translation collections:
Add/Update Stripe Invoice FROM iPaaS.com, with Add/Update Stripe Invoice Line FROM iPaaS.com
Delete Stripe Invoice FROM iPaaS.com
Update Stripe Invoice TO iPaaS.com, with Add/Update Stripe Invoice Payment TO iPaaS.com
Add/Update Stripe Sale TO iPaaS.com, with Add/Update Stripe Sale Line TO iPaaS.com, Add/Update Stripe Sale Address TO iPaaS.com and Add/Update Stripe Sale Payment TO iPaaS.com
Add/Update Stripe Customer TO iPaaS.com, with Add/Update Stripe Customer Address TO iPaaS.com
Add/Update Stripe Customer FROM iPaaS.com, with Add/Update Stripe Customer Address FROM iPaaS.com
Open the subscription's mappings (the Manage Mappings action on the subscription) and set the values below before you turn on any data flow. The collections have no Collision Handling Method; leave it unset, because the integration links records itself.
Your on-account payment method (required)
The filter of Add/Update Stripe Invoice FROM iPaaS.com sends an order or invoice that isn't cancelled, carries your on-account payment method and still has money owed, and always sends a transaction already linked to a Stripe invoice. The template can't know your method's name, so it ships this line in two places, the filter and the BalanceDue mapping of the same collection:
var onAccountMethod = "REPLACE with your on-account payment method";
Replace the text between the quotes with your method's name, exactly as in iPaaS.com, in both places. For a method named A/R:
var onAccountMethod = "A/R";
Until the filter is set, nothing is invoiced; until BalanceDue is set, an invoice asks for the whole total even when part was paid outside Stripe, and no invoice is closed as paid elsewhere. No error appears in either case. The name is compared ignoring "/", leading or trailing spaces and capitals, so A/R, AR and a/r all match. To find the name, open a recent order placed on terms and copy the Method of its on-account payment.
If your system sends unpaid invoices with no payment on them at all, the default filter passes nothing for them; ask your MiSP to adapt the filter to that system's unpaid-invoice type and status.
Your Payment Method for Stripe payments (required)
In Add/Update Stripe Invoice Payment TO iPaaS.com and Add/Update Stripe Sale Payment TO iPaaS.com, replace the Method value REPLACE with your iPaaS.com card Payment Method name with the exact name of the Payment Method you record Stripe payments with, for example Credit Card. Until you do, iPaaS.com refuses the transfer (VALD-1036): a Stripe payment doesn't update its invoice's transaction, and a sale made in Stripe isn't created.
Your SKU for Stripe items not in your catalog (required for sales)
For each line of a Stripe-made sale, the integration looks for the iPaaS.com product whose SKU is the Stripe price's lookup key, else the Stripe product's sku metadata. Set one of them on each Stripe price or product you sell (in the Stripe Dashboard, Product catalog, the product, then its price's Lookup key or the product's Metadata). For anything else, the Sku mapping of Add/Update Stripe Sale Line TO iPaaS.com uses a fallback: replace REPLACE with your SKU for Stripe items not in your catalog with the SKU of a product you keep for such items, for example MISC-STRIPE-SALE. Until you do, a sale with an unmatched line is refused (NFND-1003).
Which customers go to Stripe (choose)
By default Add/Update Stripe Customer FROM iPaaS.com sends only customers already linked to Stripe (they have a Stripe Customer ID, written by Add/Update Stripe Customer TO iPaaS.com). Keep it, or replace the last line of its filter with return !string.IsNullOrEmpty(EmailAddress); to send every customer with an email.
Optional changes
Payment status names: payments arrive with Stripe's words (Paid, Pending, Failed, Authorized, Refunded, Disputed, Won, Lost, RefundReversed, Reinstated). To use your own, change the Status mapping of both payment collections to a Lookup Translation with a row for every one of these.
Due date and currency: map DueDate or Currency in Add/Update Stripe Invoice FROM iPaaS.com if you need them; otherwise Invoice Days Until Due and your Stripe account's default currency apply.
Fields your systems set on a transaction: an update replaces the whole record, so keep the template's formulas that return the current value, and add one for any field your systems own (see Stripe to iPaaS.com Invoice Mapping Documentation).
Leave the filters of the TO iPaaS.com collections as they are. Keep exactly one Add/Update Stripe Invoice FROM iPaaS.com collection on a subscription, and don't let two subscriptions send the same transactions: give each a filter that doesn't overlap.
Turn On the Data Flows
Note: turning these on starts real work. Once the on-account payment method is set, each transaction that passes the filter gets a Stripe invoice, and Stripe emails the customer when Stripe Emails Invoices is Yes.
Stripe events (TO iPaaS.com)
Open the subscription's Inbound Data Flows (AKA External Webhooks) action and turn on these Stripe events. You don't create anything in Stripe: turning on the first event makes the integration register its own webhook endpoint in your Stripe account, named iPaaS.com with the subscription's id, and turning off the last one removes it. Don't edit or delete that endpoint in Stripe. Each subscription gets its own endpoint, and Stripe allows up to 16 per account (Stripe: "You can register up to 16 event destinations with Stripe", https://docs.stripe.com/webhooks, read 2026-11-18). Events can be turned on together or one at a time, and turned on again after they were turned off or after the Secret Key changes.
Stripe events | What they bring to iPaaS.com |
| The invoices this integration issued (status, pay link, payments), and paid Stripe invoices as orders, as the settings choose. |
| Payment Link sales, as the settings choose, and the result of a payment that settles later. |
| Payments, including ones still processing, failed, or authorized and later released. |
| Refunds made in Stripe. |
| Disputes and their outcome. |
| Stripe customers, new and changed. They also keep Add/Update Stripe Customer FROM iPaaS.com working, because they write Stripe Customer ID. |
invoice.pay_link_updated doesn't need turning on: the integration starts that transfer itself to write a new invoice's pay link back. If turning an event on fails with STRP-EXTN-1005 and you use a restricted key, add Webhook Endpoints (Write) to it, then turn the event on again.
iPaaS.com events (FROM iPaaS.com)
Open the subscription's Outbound Data Flows (formerly Internal Webhooks) action and turn on:
transaction/created,transaction/updatedand transaction/deleted: each order or invoice that passes the filter gets its Stripe invoice, later changes reach Stripe, and a deleted transaction's open invoice is voided.customer/createdand customer/updated: only if you use Add/Update Stripe Customer FROM iPaaS.com. Invoices find or create their own Stripe customer without them.
Create the Poll Events
The poll is the safety net that catches anything a webhook missed, and it is not created for you.
Go to Dashboard / Integration Monitoring / Events and click + Add Event.
Enter a Name you will recognize, for example Stripe invoice poll, and a Description, and choose the Event Type Webhook (Poll Request).
Under Event Rules, click Add for each of these rules, in this order (the Scope rule can be added only after SystemId), and click Apply after each one:
SystemId: under Expression, choose your Stripe subscription.
Scope: under Expression, choose
invoice.poll.Interval: under Expression, choose how often it runs, for example every 15 minutes.
Click Apply at the top of the event to save it.
Add a second event the same way with the scope
customer.poll.
A poll's first run looks back one hour (validate this in a staging subscription before relying on it in production). Stripe keeps events for 30 days, so if the poll is off for longer, resync the transactions and customers changed during the gap (STRP-BIZL-1002).
Test with a Test Key First
Test on a separate subscription connected to Stripe's test mode; test keys move no real money. Records the test subscription creates in iPaaS.com are real iPaaS.com records that your other integrations can see, so use a test transaction prefix and customer emails that no real customer has.
Create a test subscription with a Stripe test key (sk_test_ or rk_test_), and set its settings, custom fields and template values as above.
Narrow its Add/Update Stripe Invoice FROM iPaaS.com filter to your test transactions, so it never invoices real ones. For example, add this line above the line that starts var onAccountMethod, with a prefix you use only for tests:
if (TransactionNumber == null || !TransactionNumber.StartsWith("TEST-")) return false;Turn on its data flows and create its poll events.
Create a test order on account in iPaaS.com: a number starting with your test prefix, a line with a SKU from your catalog, an email you can read, an on-account payment and money owed.
Pay it on its pay link with Stripe's test card 4242 4242 4242 4242, any future expiry date and any three-digit CVC. Take the link from the transaction's Stripe Pay Link custom field.
Also try changing a line before paying (a new invoice numbered -R1 replaces the first), cancelling a test order (its invoice is voided), and refunding a test payment in the Stripe Dashboard (a negative payment line arrives).
When you're done, turn off the test subscription's data flows and poll events, and remove the test records.
Then go live: set up the live subscription the same way with your live key, and turn on its data flows and poll events last.
Post-Installation Verification
After completing the installation, perform these tests to verify the installation.
Data Sync Test
Data push (FROM iPaaS.com): send an order on account, or run a Manual Sync for Add/Update Stripe Invoice FROM iPaaS.com with its iPaaS.com transaction id. In the subscription's Activity Tracker, the transfer succeeds; on the transaction, Stripe Invoice ID, Stripe Pay Link and Stripe Invoice Status (Open) appear; in the Stripe Dashboard the invoice has the same number, lines and total.
Data pull (TO iPaaS.com): pay the invoice. A payment line arrives with your Payment Method, status Paid, Stripe Payment ID and Stripe Fee (the fee can be blank until Stripe settles it), and the transaction becomes Complete.
Functionality Test
Run an end-to-end business process: an order on account through to payment, and a refund in Stripe.
Validate the template values you set (the on-account method, the Payment Method, the fallback SKU) and that the data flows and poll events are on.
Review the subscription's logs and Dashboard / Integration Monitoring / Error Logs in iPaaS.com.
Orders and invoices already owed before the subscription was set up get a Stripe invoice only when they next change; to send one now, run a Manual Sync with its transaction id.
Support and Troubleshooting
Click the Help button on any iPaaS.com page to contact Support or to search our documentation.
Documentation: Search our documentation at the top of this article.
Support Portal: Click the Help and Support button at the lower-right of this window.
Contact Information: Contact iPaaS.com.
Errors appear under Dashboard / Integration Monitoring / Error Logs, and every Stripe code is explained in Stripe Error Messages. The common ones during setup:
Code or symptom | Cause | What to do |
"Unable to connect to subscription" on every transfer | The key or a setting was refused; the coded reason (STRP-AUTH-1001 to STRP-AUTH-1004, STRP-AUTZ-1001 or STRP-BIZL-1001) goes to iPaaS.com's company log, not the error list. | Check the Secret Key (a secret or restricted key, test mode outside production) and the settings' values; your MiSP can read the log entry. |
STRP-AUTH-1002 | Stripe refused the key: rolled, deleted or mistyped. | Create a new key and update Secret Key. |
STRP-AUTZ-1001 | The restricted key is missing a permission; the message names the refused call. | Add the permission to the key in Stripe. |
STRP-EXTN-1005 | The webhook endpoint couldn't be set up, often a restricted key without Webhook Endpoints (Write). | Add the permission, then turn the event on again. Records still arrive through the poll events. |
No transaction gets a Stripe invoice, and there is no error | The filter still holds REPLACE with your on-account payment method. | Set your on-account payment method in the filter and in BalanceDue. |
VALD-1036, "provided for Payment Method is not valid" | The payment Method mapping still holds the template value, or names no Payment Method in your company. | Set it to your Payment Method on both payment collections. |
NFND-1003, "Product Id … does not exist" on a sale | A Stripe item matched none of your products, and the fallback SKU isn't one of them. | Set lookup keys or sku metadata in Stripe, and the fallback SKU. |
STRP-VALD-1004, STRP-VALD-1005, STRP-VALD-1006 | No valid email, a transaction number over 22 characters, or lines that don't add up to the total. | Correct the transaction and send it again. |
STRP-BIZL-1005 | Stripe finalized the invoice for a different amount (automatic tax, or a customer credit balance), so it was voided. | Turn off Stripe automatic tax for these invoices, or clear the credit balance, then resend. |
Customer FROM iPaaS.com sends nothing | Its default filter sends only customers with a Stripe Customer ID. | Keep Add/Update Stripe Customer TO iPaaS.com on with the customer events and |
Payments don't come back | The Stripe events aren't on, or the poll events don't exist. | Turn on the events and create the poll events. |
The limits to know before going live are in Stripe Integration Known Limitations.
Security and Revoking Access
What the integration does in Stripe: it creates, emails, voids and closes the invoices it issues, finds, creates and updates Stripe customers, reads payments, refunds, disputes and Stripe-made sales, and registers its own webhook endpoint. It never charges, refunds or changes a paid invoice, and never deletes a Stripe customer.
Secrets: the Secret Key is stored encrypted and never logged. Each Stripe notice only names a record; the integration then reads that record from Stripe with your key, so a repeated or forged notice can't add a payment Stripe doesn't hold.
Revoking access: first turn off the Stripe events under Inbound Data Flows (this removes the integration's webhook endpoint from Stripe, which needs the key), then the Outbound Data Flows and the poll events. Then, if you created a restricted key for iPaaS.com, delete it under Developers > API keys. If you used the secret key, roll it only when nothing else uses it. If an endpoint named iPaaS.com is still listed under Developers > Webhooks, delete it there. Invoices already sent stay payable until they are paid or voided in Stripe.
If you used the standard secret key, don't roll it unless you know nothing else uses it: rolling it stops every other program that uses it.







