Skip to main content

Stripe Connections and Settings

How to connect the Stripe integration to iPaaS.com: the Stripe key it needs, every subscription setting with its default, how authentication works, and how throttling is set.

Integrate iPaaS.com with Stripe to bill iPaaS.com orders and invoices through Stripe invoices with a pay link, and to bring Stripe's sales, payments, refunds, disputes and customers into iPaaS.com.

How to Connect

Prerequisites

  • A Stripe account. 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).

  • A Stripe API key. In the Stripe Dashboard, open Developers > API keys and either copy the Secret key, or create a restricted key that has only the permissions the integration needs (Stripe's guide: https://docs.stripe.com/keys). Use a test-mode key on staging and test subscriptions, and a live-mode key only on your production subscription.

  • Restricted key permissions. When you create a restricted key, choose Custom permissions and set these; leave everything else 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

  • Stripe automatic tax off for these invoices. Tax comes from the iPaaS.com transaction; if Stripe adds tax, the invoice is voided rather than sent for a different amount.

Configuration Details

  • Secret Key: your Stripe secret key (it starts sk_live_ or sk_test_) or restricted key (rk_live_ or rk_test_), copied from Developers > API keys in the Stripe Dashboard. For example, a test key starts sk_test_ followed by a long string of letters and numbers. The value is stored encrypted, and the integration masks keys in its own messages; a message that quotes Stripe may show the last four characters of the key, as Stripe itself does.

  • API Url: Stripe's API address. Keep the default, https://api.stripe.com.

Configure Subscription Settings

The Stripe subscription's settings, with the Secret Key hidden.

Each optional setting takes its default when left blank. A value the integration can't use (for example "Maybe" in a Yes or No setting) stops the connection with STRP-BIZL-1001 naming the setting, so a typo never quietly becomes a default.

Field

Description

Required

Example

API Url

Stripe's API address. It must be an https address on api.stripe.com; a trailing /v1 is accepted. Blank means the default.

Yes (pre-filled with https://api.stripe.com)

https://api.stripe.com

Secret Key

The Stripe secret key or restricted key the integration uses for every call (see Authentication Methods).

Yes

sk_test_…

Stripe Emails Invoices

Yes: Stripe emails each new invoice, with its pay link, to the customer. No: the integration doesn't ask Stripe to send it, and you send the link yourself. Default Yes. Stripe sends no invoice emails from a test key.

No

Yes

Invoice Days Until Due

Days from issue until a Stripe invoice is due, used when no due date is mapped. A whole number from 1 to 365. Default 30.

No

30

Close Stripe Invoices Paid Elsewhere

Yes: when a transaction's balance reaches 0 through payments made outside Stripe, its open Stripe invoice is marked paid outside Stripe so the customer can't pay twice (no money moves). No: the invoice stays open and the warning STRP-BIZL-1010 says so. Default Yes.

No

Yes

Bring In Payment Link Sales

Yes: a completed Stripe Payment Link checkout arrives in iPaaS.com as an order. Default Yes.

No

Yes

Bring In Subscription Invoices

Yes: a paid Stripe subscription invoice arrives in iPaaS.com as an order. Set No when your subscriptions already reach your ERP another way. Default Yes.

No

Yes

Bring In Other Invoices

Yes: a paid Stripe invoice made in the Stripe Dashboard or by another system arrives as an order. Default No.

No

No

Skip Objects Marked In Metadata

A Stripe metadata key. An invoice or Checkout Session (or its subscription) carrying that key never arrives in iPaaS.com; use it when another system already brings those sales in. At most 40 characters, no spaces or brackets. Default blank (nothing skipped).

No

other_billing_system

Yes or No settings also accept true or false. The throttling fields on the same page are described under Throttling.

Authentication Methods

  1. Copy your Stripe secret key or restricted key (see Prerequisites) and paste it into Secret Key.

  2. Save the subscription. Before each connection, the integration checks the key and the settings without calling Stripe:

    • a blank key is refused with STRP-AUTH-1001;

    • a publishable key (pk_), or a value that isn't a Stripe secret or restricted key, is refused with STRP-AUTH-1003;

    • a live key (sk_live_ or rk_live_) outside iPaaS.com production is refused with STRP-AUTH-1004, because live keys charge real cards;

    • an API Url that isn't https on api.stripe.com, or an optional setting it can't use, is refused with STRP-BIZL-1001.

  3. The integration then reads your Stripe account once to prove the key, and sends the key as a bearer token on every call to Stripe. Every call uses Stripe API version 2026-09-30.endive, whatever your account's default version is.

  4. A key Stripe refuses (rolled, expired or deleted) gives STRP-AUTH-1002; a restricted key missing a permission gives STRP-AUTZ-1001, naming the refused call.

When a key or setting is refused, each transfer shows "Unable to connect to subscription" in Dashboard / Integration Monitoring / Error Logs, and the coded reason is written to iPaaS.com's company log rather than the error list. The causes are the ones listed in this section: a blank key (STRP-AUTH-1001), a publishable or unrecognised key (STRP-AUTH-1003), a live key outside production (STRP-AUTH-1004), a refused key (STRP-AUTH-1002), a missing permission (STRP-AUTZ-1001) or a setting that can't be used (STRP-BIZL-1001); your MiSP can read the log entry if the cause isn't clear.

Rotating the key: create or roll the key in Stripe (Developers > API keys), paste the new one into Secret Key and save. Stripe lets you roll a key with an expiry, so the old key keeps working until then (Stripe API keys documentation, https://docs.stripe.com/keys, read 2026-11-20); update the subscription during that window. The webhook endpoint the integration registered stays in place, and Stripe events can be turned on and off as usual after the key changes.

Webhooks: you don't set up anything in Stripe by hand. Turning on a Stripe event under the subscription's Inbound Data Flows makes the integration create and maintain this subscription's webhook endpoint in your Stripe account, which needs the Webhook Endpoints (Write) permission on a restricted key.

Initialization Support

Currently, initialization is not supported for Stripe in iPaaS.com. All data synchronization and mappings must be configured manually during the integration process. Records move as they change, through Stripe events, the invoice.poll and customer.poll scheduled events, and transaction and customer events FROM iPaaS.com; use Manual Sync for records created before the integration was set up (see Stripe Integration Known Limitations).

Throttling

Throttling keeps the integration within Stripe's API limits, preserving performance during heavy data transfers. Stripe allows 100 requests per second in live mode and 25 in a sandbox (https://docs.stripe.com/rate-limits, read 2026-11-18). When Stripe asks the integration to slow down, the transfer is rescheduled automatically (STRP-EXTN-1003); no action is needed.

While the throttling fields (Concurrent Connections, Concurrent Batch Executions, API Throttle Limit and API Throttle Seconds, with their (To iPaaS) counterparts) are required, the values are pre-populated by the integration settings. Lower Concurrent Connections if STRP-EXTN-1003 appears often. For more details, refer to Subscription Configuration – Edit.

Related Documents

Did this answer your question?