Skip to main content

Stripe to iPaaS.com Sale Mapping Documentation

How the Stripe integration brings sales Stripe made, such as paid subscription invoices and Payment Link checkouts, TO iPaaS.com as orders with their lines, addresses and payments, and adds later refunds and disputes as payment lines.

Contents

Summary

iPaaS.com orders can be transferred from Stripe sales through Stripe webhooks, a scheduled poll and Manual Sync. A sale is something Stripe made on its own: a paid subscription invoice, a completed Payment Link checkout, and (when you choose) another paid Stripe invoice made in the Stripe Dashboard or by another system. Each sale arrives as an iPaaS.com order with its lines, billing and shipping addresses, tax, shipping, discount, total and payments; refunds and disputes that happen later are added to the same order as new payment lines.

Invoices that this integration issued for iPaaS.com transactions don't arrive here: they update their own transaction through Update Stripe Invoice TO iPaaS.com (see Stripe to iPaaS.com Invoice Mapping Documentation).

Three settings, described in Stripe Connections and Settings, choose which sales arrive:

Setting

Default

What it does

Bring In Subscription Invoices

Yes

A paid Stripe subscription invoice becomes an order.

Bring In Payment Link Sales

Yes

A completed Stripe Payment Link checkout becomes an order.

Bring In Other Invoices

No

A paid Stripe invoice made in the Stripe Dashboard or by another system becomes an order.

A fourth setting, Skip Objects Marked In Metadata, names a Stripe metadata key: an invoice or Checkout Session (or its subscription) carrying that key never arrives. Use it when another system already brings those sales into iPaaS.com.

ID Format

Manual Sync ID Format

Enter the Stripe id of the sale on the iPaaS.com Manual Sync page:

  • A sale from an invoice: the Stripe invoice id (it starts in_), for example in_1UcrUV5scPVYZfHF5jsQvo9D.

  • A Payment Link sale: the Stripe Checkout Session id (it starts cs_).

The id of a payment, charge, refund or dispute on the sale (it starts pi_, ch_, py_, re_ or du_) also finds the sale it belongs to. An id that belongs to no sale to bring in (an unpaid invoice, an invoice this integration issued, a checkout made by another system's code) transfers nothing and logs no error.

External ID Format

iPaaS.com saves the Stripe invoice id, or for a Payment Link sale the Checkout Session id, as the external ID on its own external-ID record, which is how a later event finds the same order. The default template also maps the Stripe invoice number (for example UFQTNGNL-0001), or the Checkout Session id for a Payment Link sale, into the order's TransactionNumber.

The child records are linked the same way, each by the sale's external ID followed by its own id:

  • A line: the sale's id, a vertical bar, then the Stripe line id.

  • An address: the sale's id, a vertical bar, then billing or shipping, for example in_1UcrUV5scPVYZfHF5jsQvo9D|billing.

  • A payment line: the sale's id, a vertical bar, then the Stripe payment, refund or dispute id (it starts pi_, re_ or du_). A reversal (a refund that failed, a dispute won) adds -reversal to the id.

Deleted Record Support

Not supported. Stripe doesn't delete a paid invoice or a completed checkout, and nothing in iPaaS.com is deleted when a sale changes in Stripe. A refund or dispute is added to the order as a payment line instead, and the order keeps the Status your systems gave it.

Custom Field Support

The collections write these iPaaS.com custom fields, which must exist before the first transfer:

Custom field

On

Value

Stripe Invoice ID

Transaction

For a sale from an invoice: the Stripe invoice id (it starts in_).

Stripe Checkout Session ID

Transaction

For a Payment Link sale: the Stripe Checkout Session id (it starts cs_).

Stripe Invoice Status

Transaction

The sale's state in Stripe: Paid, PartiallyRefunded, Refunded, Disputed or PaidWithCredit.

Stripe Amount Paid

Transaction

The money Stripe received, less refunds and money held by disputes.

Stripe Payment ID

Transaction Payment

The Stripe payment, refund or dispute id.

Stripe Fee

Transaction Payment

Stripe's processing fee, or the dispute fee.

A sale also offers these Stripe values, which you can map to further custom fields you add with + Add Custom Field in the mapping editor: StripeSubscriptionId (it starts sub_), StripePaymentLinkId (it starts plink_), StripeCustomerId (it starts cus_), Currency, InvoicePdf, CreatedAt and PaidAt.

Stripe metadata: each metadata key on the Stripe invoice or Checkout Session arrives as a custom field of the Stripe record, so a Dynamic Formula can read one with var f = CustomFields == null ? null : CustomFields.FirstOrDefault(x => x.Key == "your key"); return f == null ? null : f.Value; and map it to any iPaaS.com field or custom field. More Stripe values: every other value Stripe holds for the invoice or Checkout Session is offered too, for example the amount due, amounts paid in and outside Stripe, starting and ending balances, credit notes, the collection method, finalized, voided and next-attempt times, the receipt number, tax and discount amounts (Taxes, Discounts), the customer's tax ids, Stripe's own custom fields, and, under Details, Stripe's settings for the invoice or Checkout Session as name and value pairs (for example payment_settings.payment_method_types). Lines and payments offer the same: each line's period, price, tax and discount amounts and metadata; each payment's charge, card brand, funding and country (never the card number, expiry or fingerprint), receipt, failure reason, refund and dispute details. Stripe's payment secrets (client secrets) are never brought into iPaaS.com. For a Payment Link sale this includes the session's payment status, mode, locale, customer name and business name, the pages it returns to, and when it expires.

Mapping Collection Status

  • Status: Enabled.

  • Trigger Events: the Stripe events you turn on under the subscription's Inbound Data Flows. invoice.paid brings in a sale from an invoice; checkout.session.completed and checkout.session.async_payment_succeeded bring in a Payment Link sale. Later payment changes arrive through payment_intent.succeeded, payment_intent.processing, payment_intent.payment_failed, payment_intent.canceled, checkout.session.async_payment_failed, charge.refunded, refund.created, refund.updated, refund.failed, charge.dispute.created, charge.dispute.updated, charge.dispute.closed, charge.dispute.funds_withdrawn and charge.dispute.funds_reinstated. A scheduled iPaaS.com Event with the scope invoice.poll catches anything a webhook missed, and Manual Sync is available by Stripe id. The child collections transfer with the sale.

Duplicate or Conflicting Mappings

  • Update Stripe Invoice TO iPaaS.com also brings Stripe transactions into iPaaS.com. The two collections are separated by Kind: this collection takes Sale, that one takes Invoice (the invoices this integration issued). Keep both filters' Kind conditions as they are, so each Stripe record reaches exactly one collection.

  • Another system's Stripe sales: if another system also brings Stripe sales into iPaaS.com, set Skip Objects Marked In Metadata to the metadata key that system writes, or turn off the matching Bring In setting, so nothing arrives twice.

Record Matching

The collection has no Collision Handling Method. One order per Stripe sale is kept by the external ID: repeated webhooks, the poll and a Manual Sync of the same sale update the same order, and each payment line is matched by its Stripe id, so a payment is never added twice. The integration doesn't look for an existing iPaaS.com order to link to. When no external-ID record exists and another iPaaS.com transaction already holds the sale's number in TransactionNumber, iPaaS.com refuses the transfer as a duplicate rather than linking to it.

Unmapped Field Overwrite Risk

An update replaces the whole record, so a field these collections don't map can be cleared when the sale transfers again (a refund or dispute transfers it again). The template keeps every field Stripe doesn't own with a formula that returns the value already on the record, for example return DestinationValue != null ? (object)DestinationValue.TransactionCreatedDateTime : null;:

  • Order: CompanyId, ParentId, SystemId, Status, TransactionNumber, TransactionCreatedDateTime and TransactionUpdatedDateTime.

  • Line: SequenceNumber, QtyShipped, OriginalUnitPrice, DiscountPercent, TaxPercent, EstimatedTaxAmount and Weight.

  • Address: Company, Address3, ShippingMethod, ShippingMethodDescription, ShippingAmount and ShipDate.

Keep every mapping: a field whose mapping is removed is written empty on the next update. LineInfo (a nested line detail) isn't mapped and isn't cleared.

Supported Child Collections

  • Add/Update Stripe Sale Line TO iPaaS.com (Transaction Line): the sale's lines, each linked by its Stripe line id.

  • Add/Update Stripe Sale Address TO iPaaS.com (Transaction Address): the billing address and, when Stripe has one, the shipping address.

  • Add/Update Stripe Sale Payment TO iPaaS.com (Transaction Payment): the payment, and a payment line for each refund, dispute and reversal.

System Caveats

Stripe Caveats

  • Products: a line's SKU comes from the Stripe price's lookup key, or else from the Stripe product's sku metadata. Give your Stripe prices or products the same SKUs as your iPaaS.com products.

  • One name on an address: Stripe keeps a single name on an address, so a two-part name is split into first and last name (the last word is the last name).

  • Payments that settle later: a sale arrives only once its payment succeeds: a bank debit that is still processing, or one that fails, brings in no sale. A payment captured later arrives as Authorized.

  • Rate limiting: when Stripe asks the integration to slow down, the transfer is rescheduled automatically and resumes after the wait. No action is needed.

iPaaS.com Caveats

  • A sale's customer is set only when the sale is created. Before a new order is created, the integration brings its Stripe customer into iPaaS.com through Add/Update Stripe Customer TO iPaaS.com, so the order is created with its customer. 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), the order is still created: iPaaS.com may link it to the iPaaS.com customer with the buyer's email; otherwise it has no customer.

  • Products must exist: every line is a Product line, so its SKU must be an iPaaS.com product or variant. iPaaS.com refuses the whole sale when one line's SKU isn't.

  • Payment Method: every payment line needs a Payment Method that exists in iPaaS.com, named in the Method mapping of Add/Update Stripe Sale Payment TO iPaaS.com.

  • Payment status is text: iPaaS.com stores a payment line's status as text, so Stripe's status words are saved as they are.

  • Child collections move with the sale: don't add the line, address or payment collection as a collection of its own. A record sent on its own is refused.

Setup Requirements

Stripe Configuration

  • Secret Key: a Stripe secret key or restricted key with the permissions listed in Stripe Installation Instructions.

  • Product SKUs: a lookup key on each Stripe price you sell, or sku metadata on each Stripe product, set to the matching iPaaS.com SKU.

iPaaS.com Configuration

  • Settings: Bring In Subscription Invoices, Bring In Payment Link Sales, Bring In Other Invoices and Skip Objects Marked In Metadata (see Stripe Connections and Settings).

  • Webhooks: turn on the Stripe events you want under the subscription's Inbound Data Flows. The integration creates and maintains this subscription's Stripe webhook endpoint for you; turning the last event off removes it.

  • Poll: a scheduled iPaaS.com Event with the scope invoice.poll, for example every 15 minutes.

  • Custom fields: the six custom fields listed under Custom Field Support.

  • Fallback SKU and Payment Method: replace the two "REPLACE with" values described under Mappings before the first transfer.

Integration Flow

  1. A Stripe webhook, the invoice.poll Event or a Manual Sync names a Stripe record.

  2. The integration reads it from Stripe and finds the sale it belongs to: the invoice (with its lines and payments) or the Payment Link's Checkout Session (with its line items), and each payment's charge, refunds and disputes.

  3. It decides whether it is a sale to bring in: not an invoice this integration issued, allowed by the Bring In settings, and not marked with the Skip Objects Marked In Metadata key. Anything else transfers nothing and logs no error.

  4. It matches each line to an iPaaS.com product by SKU (the Stripe price's lookup key, else the Stripe product's sku metadata).

  5. For a new sale whose Stripe customer isn't in iPaaS.com yet, it brings that customer in first through Add/Update Stripe Customer TO iPaaS.com. If the customer can't be brought in, the sale still continues without the integration's customer link.

  6. The sale passes the collection's filter (it must be a Sale) and is mapped through Add/Update Stripe Sale TO iPaaS.com, and its lines, addresses and payments through the three child collections.

  7. iPaaS.com creates the order, or updates the one linked to the sale's external ID. A refund, dispute or reversal adds a payment line; a line already posted never changes its amount.

Mappings

Single-line formulas in the tables are shown without the one-line explanatory comment the template puts above them; the logic is the same.

Add/Update Stripe Sale TO iPaaS.com

iPaaS.com data type: Transaction

Mapping Filter

// Leave as is: only sales Stripe made (the settings Bring In Payment Link Sales, Bring In Subscription Invoices and Bring In Other Invoices choose which).
return Kind == "Sale";

Filter Description: only Stripe-made sales are processed (Kind is Sale); invoices this integration issued (Kind is Invoice) are left to Update Stripe Invoice TO iPaaS.com. A record that fails the filter is skipped with no error. Which Stripe-made sales count is decided by the settings above, not by the filter. Leave the filter as it is.

Description: creates or updates an iPaaS.com order for each Stripe-made sale, with its customer, totals and Stripe state.

Mapping Type

Source Field (Stripe)

Destination Field (iPaaS.com)

Description

Dynamic Formula

return DestinationValue != null ? DestinationValue.CompanyId : null;

CompanyId

Recommended. Keeps the company your systems gave the order: a new sale has none, and an update keeps the one it has. Leave this mapping in place, or a later refund or dispute would clear the company.

Field

IpaasCustomerId

CustomerId

Recommended. iPaaS.com needs a customer, a company or an email on every transaction. The iPaaS.com customer linked to the sale's Stripe customer, brought in first for a new sale. iPaaS.com sets an order's customer only when it creates the order.

Field

DiscountAmount

DiscountAmount

Recommended. The discount Stripe applied to the whole sale, as a positive amount; 0 when there is none.

Field

CustomerEmail

EmailAddress

Recommended. The buyer's email as Stripe has it: the invoice's customer email, or the email entered at a Payment Link checkout.

Dynamic Formula

return DestinationValue != null ? (object)DestinationValue.ParentId : null;

ParentId

Recommended. Keeps the parent transaction your systems gave the order. Leave this mapping in place, or a later refund or dispute would clear it.

Field

ShippingAmount

ShippingAmount

Recommended. The shipping Stripe charged: the invoice's shipping amount, or the shipping rate chosen at checkout; 0 when there is none.

Dynamic Formula

return DestinationValue != null ? DestinationValue.Status : "Complete";

Status

Required. A new sale is created as Complete; an update keeps the status your systems set (for example Shipped or Cancelled). The sale's Stripe state is in Stripe Invoice Status.

Field

AmountPaid

Stripe Amount Paid

Recommended. The money Stripe received, less refunds and money held by disputes; it changes as refunds and disputes arrive.

Field

StripeCheckoutSessionId

Stripe Checkout Session ID

Recommended. For a Payment Link sale, the Checkout Session id (it starts cs_); blank for a sale from an invoice.

Field

StripeInvoiceId

Stripe Invoice ID

Recommended. For a sale from an invoice, the Stripe invoice id (it starts in_); blank for a Payment Link sale.

Field

Status

Stripe Invoice Status

Recommended. The sale's state in Stripe: Paid, PartiallyRefunded (paid in full, then part refunded), Refunded, Disputed (a dispute is open or was lost) or PaidWithCredit (Stripe closed the invoice for less with a credit note).

Field

Subtotal

Subtotal

Recommended. The total of the sale's lines before tax, shipping and discount.

Dynamic Formula

return DestinationValue != null ? (object)DestinationValue.SystemId : SpaceportSystemId;

SystemId

Required. This Stripe subscription for a new sale; an update keeps the system the order has.

Field

TaxAmount

TaxAmount

Recommended. The tax Stripe charged: the invoice's taxes added up, or the checkout's tax; 0 when there is none.

Field

Total

Total

Recommended. What the buyer was charged: the lines plus tax and shipping, less the discount. It doesn't change when a refund or dispute arrives.

Dynamic Formula

return Lines == null ? 0 : Lines.Sum(l => l.Quantity ?? 0);

TotalQty

Optional. The number of items: the sale's line quantities added up.

Dynamic Formula

return DestinationValue != null ? DestinationValue.TransactionNumber : (TransactionNumber != null ? TransactionNumber : StripeCheckoutSessionId);

TransactionNumber

Required. The Stripe invoice number, or the Checkout Session id for a Payment Link sale (Stripe gives a checkout no number); an update keeps the order's number.

Static

"Order"

Type

Required. Every Stripe sale arrives as an Order. Change it only if your systems expect Stripe sales as another transaction type.

Dynamic Formula

return DestinationValue != null ? (object)DestinationValue.TransactionCreatedDateTime : null;

TransactionCreatedDateTime

Optional. Keeps the value your systems set: Stripe has no TransactionCreatedDateTime, and an update replaces the whole record.

Dynamic Formula

return DestinationValue != null ? (object)DestinationValue.TransactionUpdatedDateTime : null;

TransactionUpdatedDateTime

Optional. Keeps the value your systems set: Stripe has no TransactionUpdatedDateTime, and an update replaces the whole record.

Add/Update Stripe Sale Line TO iPaaS.com

iPaaS.com data type: Transaction Line

Description: writes each line of the sale onto its order: what was bought, how many, the unit price, the line total and the line's discount, matched to an iPaaS.com product by SKU.

Mapping Type

Source Field (Stripe)

Destination Field (iPaaS.com)

Description

Field

Description

Description

Recommended. What the buyer bought, as the Stripe invoice line or Payment Link item describes it.

Field

DiscountAmount

DiscountAmount

Recommended. The discount Stripe applied to this line, as a positive amount; 0 when there is none.

Field

ExtendedPrice

ExtendedPrice

Recommended. The line's total (quantity × unit price), after any line discount, before tax.

Field

Quantity

Qty

Recommended. How many the buyer bought.

Dynamic Formula

return CatalogSku != null ? CatalogSku : "REPLACE with your SKU for Stripe items not in your catalog";

Sku

Required. CatalogSku is the SKU of the iPaaS.com product the Stripe line matches (the price's lookup key, else the product's sku metadata); when nothing matches, the formula's fallback is used.

Static

"Complete"

Status

Required. Every line of a Stripe sale arrives as Complete: Stripe sends a sale once checkout or payment is done.

Static

"Product"

Type

Required. Every line is a Product line, so its SKU must be an iPaaS.com product or variant.

Field

UnitPrice

UnitPrice

Recommended. The price of one, in the sale's currency, after any line discount.

Dynamic Formula

return DestinationValue != null ? (object)DestinationValue.SequenceNumber : null;

SequenceNumber

Optional. Keeps the value your systems set: Stripe has no SequenceNumber, and an update replaces the whole record.

Dynamic Formula

return DestinationValue != null ? (object)DestinationValue.QtyShipped : null;

QtyShipped

Optional. Keeps the value your systems set: Stripe has no QtyShipped, and an update replaces the whole record.

Dynamic Formula

return DestinationValue != null ? (object)DestinationValue.OriginalUnitPrice : null;

OriginalUnitPrice

Optional. Keeps the value your systems set: Stripe has no OriginalUnitPrice, and an update replaces the whole record.

Dynamic Formula

return DestinationValue != null ? (object)DestinationValue.DiscountPercent : null;

DiscountPercent

Optional. Keeps the value your systems set: Stripe has no DiscountPercent, and an update replaces the whole record.

Dynamic Formula

return DestinationValue != null ? (object)DestinationValue.TaxPercent : null;

TaxPercent

Optional. Keeps the value your systems set: Stripe has no TaxPercent, and an update replaces the whole record.

Dynamic Formula

return DestinationValue != null ? (object)DestinationValue.EstimatedTaxAmount : null;

EstimatedTaxAmount

Optional. Keeps the value your systems set: Stripe has no EstimatedTaxAmount, and an update replaces the whole record.

Dynamic Formula

return DestinationValue != null ? (object)DestinationValue.Weight : null;

Weight

Optional. Keeps the value your systems set: Stripe has no Weight, and an update replaces the whole record.

Placeholder value — replace during implementation: the Sku fallback "REPLACE with your SKU for Stripe items not in your catalog". Replace it with the SKU of an iPaaS.com product you keep for Stripe sales you can't match (for example MISC-STRIPE-SALE), or give every Stripe price a lookup key, or every Stripe product sku metadata, that matches an iPaaS.com SKU. One of these must be done before the first transfer; until it is, iPaaS.com refuses a sale with an unmatched line (see Error Handling).

Add/Update Stripe Sale Address TO iPaaS.com

iPaaS.com data type: Transaction Address

Description: writes the sale's billing address (the invoice's customer address, or the address entered at a Payment Link checkout) and, when Stripe has one, its shipping address.

Mapping Type

Source Field (Stripe)

Destination Field (iPaaS.com)

Description

Field

Line1

Address1

Recommended. Street address, line 1.

Field

Line2

Address2

Optional. Street address, line 2.

Field

City

City

Recommended. City.

Field

Country

Country

Recommended. The two-letter country code Stripe stores (for example US).

Field

FirstName

FirstName

Recommended. The name on the address without its last word.

Field

IsPrimaryBilling

IsPrimaryBilling

Recommended. True for the billing address.

Field

IsPrimaryShipping

IsPrimaryShipping

Recommended. True for the shipping address.

Field

LastName

LastName

Recommended. The last word of the name on the address.

Field

PostalCode

PostalCode

Recommended. Postal or ZIP code.

Field

State

Region

Recommended. State, province or region, as Stripe stores it.

Dynamic Formula

return DestinationValue != null ? (object)DestinationValue.Address3 : null;

Address3

Optional. Keeps the value your systems set: Stripe has no Address3, and an update replaces the whole record.

Dynamic Formula

return DestinationValue != null ? (object)DestinationValue.ShippingMethod : null;

ShippingMethod

Optional. Keeps the value your systems set: Stripe has no ShippingMethod, and an update replaces the whole record.

Dynamic Formula

return DestinationValue != null ? (object)DestinationValue.ShippingMethodDescription : null;

ShippingMethodDescription

Optional. Keeps the value your systems set: Stripe has no ShippingMethodDescription, and an update replaces the whole record.

Dynamic Formula

return DestinationValue != null ? (object)DestinationValue.ShippingAmount : null;

ShippingAmount

Optional. Keeps the value your systems set: Stripe has no ShippingAmount, and an update replaces the whole record.

Dynamic Formula

return DestinationValue != null ? (object)DestinationValue.ShipDate : null;

ShipDate

Optional. Keeps the value your systems set: Stripe has no ShipDate, and an update replaces the whole record.

Dynamic Formula

return DestinationValue != null ? (object)DestinationValue.Company : null;

Company

Optional. Keeps the value your systems set: Stripe has no Company, and an update replaces the whole record.

Add/Update Stripe Sale Payment TO iPaaS.com

iPaaS.com data type: Transaction Payment

Description: writes the sale's payment, and a payment line for each refund, dispute and reversal that happens later. A line's amount never changes once it is posted.

Mapping Type

Source Field (Stripe)

Destination Field (iPaaS.com)

Description

Field

Amount

Amount

Required. Positive for a payment and for money given back to you (a refund that failed, a dispute won), negative for a refund and a dispute. Keep this mapping: without it a new payment line is written as 0.00.

Field

Description

Description

Recommended. A short description of the line, for example the Stripe payment id with the card brand and last four digits.

Static

"REPLACE with your iPaaS.com card Payment Method name"

Method

Required. The name of a Payment Method configured in iPaaS.com.

Field

Status

Status

Recommended. The line's state in Stripe's words (see the values below).

Field

StripeFee

Stripe Fee

Optional. What Stripe charged for this line (its processing fee, or the dispute fee); blank until Stripe has settled it.

Field

StripePaymentId

Stripe Payment ID

Recommended. Stripe's id for the line: the payment (it starts pi_), refund (re_) or dispute (du_).

Placeholder value — replace during implementation: the Method value "REPLACE with your iPaaS.com card Payment Method name". Change it to the name of the Payment Method you use for Stripe payments, exactly as configured in iPaaS.com (for example Credit Card). This must be done before the first transfer; until it is, iPaaS.com refuses the sale (see Error Handling).

Payment statuses: a payment is Paid, or Authorized when it is captured later. A sale arrives only once its payment has succeeded or been authorized, so a bank debit that is still processing, or one that fails, brings in no sale. A refund is Refunded or Pending. A dispute is Disputed, Won or Lost. Money given back is RefundReversed or Reinstated. To use your own status names, change the Status mapping to a Lookup Translation that covers every value; a value with no translation row is saved with an empty status.

Only the card brand and last four digits reach iPaaS.com; no field can hold a card number.

Error Handling

Errors appear in iPaaS.com Dashboard / Integration Monitoring / Error Logs. Every Stripe error code is described in Stripe Error Messages.

  • "NFND-1003 - Product Id: REPLACE with your SKU for Stripe items not in your catalog does not exist or can not be found." A line matched none of your products and the Sku fallback is still the template value, or isn't one of your products (the message names the SKU sent). iPaaS.com refuses the whole sale. Resolution: give the Stripe price a lookup key or the product sku metadata, or set the fallback to one of your SKUs, then run a Manual Sync with the sale's Stripe id.

  • "VALD-1036 - Value (REPLACE with your iPaaS.com card Payment Method name) provided for Payment Method is not valid." The Method mapping still holds the template value, or names a Payment Method that doesn't exist in iPaaS.com (the message names the value sent). Resolution: create the Payment Method, or change the mapping to yours, then resend the sale.

  • STRP-BIZL-1009: "Stripe customer … has the email …, which iPaaS.com customer … already has, linked to Stripe customer …" The sale's Stripe customer couldn't be brought in because its email belongs to another linked customer. The sale still arrives, without the integration's customer link. Resolution: merge the two customers in Stripe, or give this one its own email.

  • STRP-BIZL-1011: "This record moves with its transaction or customer, never on its own." A line, address or payment collection was added as a collection of its own. Resolution: remove that collection, and send the sale instead.

  • STRP-EXTN-1003 (Stripe rate limit) and STRP-EXTN-1002 (Stripe temporarily unavailable). Stripe limited the number of calls or didn't answer. Resolution: nothing; the transfer is retried. Lower Concurrent Connections if the rate limit appears often.

  • STRP-AUTH-1002 (Secret Key refused) and STRP-AUTZ-1001 (restricted key lacks a permission). Resolution: create the key again in Stripe, or add the permission the message names, and update Secret Key.

A Stripe record that isn't a sale to bring in (see Integration Flow, step 3) transfers nothing and is not an error.

Testing and Validation

Test Scenarios

  1. In Stripe test mode, create a subscription whose price has a lookup key equal to one of your iPaaS.com SKUs. When its first invoice is paid, confirm an order arrives: status Complete, the Stripe invoice number as its number, the line with your SKU, the billing address, a Paid payment line with its Stripe Fee, and Stripe Invoice ID.

  2. If you use Bring In Payment Link Sales, complete a test checkout through a Stripe Payment Link with a shipping address. Confirm an order arrives with the Checkout Session id as its number, Stripe Checkout Session ID, the lines and both addresses.

  3. Sell an item that matches none of your products. Confirm the line carries your fallback SKU.

  4. Refund part of a sale in Stripe. Confirm a negative Refunded payment line is added, Stripe Invoice Status reads PartiallyRefunded, and the order's Status is unchanged.

  5. Pay an invoice made in the Stripe Dashboard with Bring In Other Invoices at No. Confirm nothing arrives and no error is logged.

  6. Run a Manual Sync with a sale's Stripe invoice id. Confirm the same order is updated and no second order or payment line appears.

Validation Checklist

  • The Bring In settings match the Stripe sales you want.

  • Each Stripe price or product you sell has a lookup key or sku metadata with your iPaaS.com SKU, and the fallback SKU is one of your products.

  • The payment Method names a Payment Method that exists in iPaaS.com.

  • The six custom fields exist.

  • The invoice.poll Event is scheduled, and the Stripe events you want are on under Inbound Data Flows.

Additional Notes

  • No money moves from iPaaS.com: no charge, refund or credit note is made in Stripe from iPaaS.com. Refunds and disputes are handled in Stripe and only reported here.

  • Initial load: sales made in Stripe before the integration was set up are not brought in automatically; use Manual Sync for any you need.

  • A wrong customer link: a sale created without a customer, or linked by email to a customer you didn't expect, is corrected only by deleting the order in iPaaS.com and syncing it again once the customer is in iPaaS.com. See Stripe Integration Known Limitations.

Related Documents

Related Mapping Documentation

Did this answer your question?