Overview
This article catalogs the errors subscribers can encounter with the Stripe integration. Each error carries a stable code you can search for on this page, followed by what triggers it and what to do. Errors appear in iPaaS.com under Dashboard / Integration Monitoring / Error Logs.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Some resolutions refer to your Managed Integration Service Provider (MiSP): the partner who set up and manages your iPaaS.com integration (its mappings, settings and credentials). For an error not covered here, give your MiSP the iPaaS.com subscription id, the transaction number, the Stripe ids on the record (Stripe Invoice ID, Stripe Checkout Session ID, Stripe Payment ID or Stripe Customer ID) and the error log entry.
Codes with two parts and no STRP- prefix (for example NFND-1003 or VALD-1036) come from iPaaS.com itself, not from this integration; the Stripe Installation Instructions explain the ones a new subscription most often meets.
Every message is logged in the form {code} - {message} - {the address of the Stripe error messages help article}. In the messages below, words in braces are filled in when the error happens, for example {transaction number}. Keys and webhook keys are never shown in a message: they are masked.
Supported Flows
Some situations are expected and log no error, for example a transaction the collection's filter doesn't pass, or a transaction sent again with nothing changed. They are listed in Stripe Integration Known Limitations, item 31.
Error Collection
Authentication and connection validation
These errors are found when the integration connects, before any record moves, so every transfer of the subscription fails until the cause is fixed. The transfer's error then shows only "Unable to connect to subscription": the coded reason is written to iPaaS.com's company log, not to the error list, so your MiSP can read it there. Once the cause is fixed, resend any record still in the error log. To find the cause yourself, check the settings in this order: Secret Key is filled in; it is a secret key (sk_) or restricted key (rk_), not a publishable key (pk_); it is a test key on a test subscription and a live key only in production; it hasn't been rolled or deleted in Stripe; a restricted key has every permission the installation instructions list; API Url is https://api.stripe.com (or blank), with nothing after it; and each optional setting holds a value it allows.
The Secret Key is missing
STRP-AUTH-1001 - The Secret Key setting is required: a Stripe secret key (sk_…) or a restricted key (rk_…) from Stripe's Dashboard → Developers → API keys.
STRP-AUTH-1001 - The subscription's settings couldn't be read.
Description: The first form: the subscription has no Secret Key. The second form: iPaaS.com didn't hand the integration the subscription's settings. This fires before any call to Stripe.
Resolution: In the Stripe Dashboard, open Developers → API keys, copy the secret key, or create a restricted key with the permissions the installation instructions list, paste it into Secret Key on the subscription, and save. If the second form persists with the settings filled in, raise it with your MiSP, then iPaaS.com Support.
Stripe refused the Secret Key
STRP-AUTH-1002 - Stripe refused the Secret Key for {action} (401). Check the subscription's Secret Key (Stripe Dashboard → Developers → API keys): it may have been rolled or deleted.
Description: Stripe answered HTTP 401: the key was rolled, deleted or mistyped.
{action}is what the integration was doing, for example "the connection check (read the Stripe account)".Resolution: In the Stripe Dashboard, open Developers → API keys, create or reveal the key again, and update Secret Key on the subscription.
The key isn't a secret or restricted key
STRP-AUTH-1003 - The Secret Key is a publishable key (pk_…), which can't read or write anything this integration needs. Use the secret key (sk_…) or a restricted key (rk_…).
STRP-AUTH-1003 - The Secret Key doesn't look like a Stripe secret or restricted key (sk_live_, rk_live_, sk_test_ or rk_test_). Copy it again from Stripe's Dashboard → Developers → API keys.
Description: The Secret Key holds a publishable key, which is meant for web pages and can't be used by the integration (the first form), or a value that isn't a Stripe key at all, often a partial copy (the second form). This fires before any call to Stripe.
Resolution: Copy the secret key (
sk_…) or a restricted key (rk_…) in full from Developers → API keys, paste it into Secret Key, and save.
A live key outside iPaaS.com production
STRP-AUTH-1004 - A live Stripe key is refused outside iPaaS.com production: live keys charge real cards and move real money. Use a test key (sk_test_ or rk_test_) on this environment.
Description: The Secret Key is a live key (
sk_live_orrk_live_), and the subscription is not in iPaaS.com production. Live keys charge real cards, so they are refused before any call to Stripe.Resolution: On a staging or test subscription, use a Stripe test-mode key (
sk_test_orrk_test_). Use the live key only on your production subscription. If this appears on your production subscription, raise it with your MiSP, then iPaaS.com Support: the platform didn't identify the subscription as production. A test key is not refused in production, so check that your production subscription holds the live key before you go live.
The restricted key lacks a permission
STRP-AUTZ-1001 - Stripe refused {action} (403): the restricted key lacks a permission this needs ({Stripe's message}). Add the permission to the key in Stripe (Developers → API keys), as the installation instructions list.
STRP-AUTZ-1001 - Stripe answered the connection check without naming the account. A restricted key needs the Account (read) permission.
Description: The Secret Key is a restricted key that is missing a permission. The first form: Stripe answered HTTP 403 to a call;
{action}and Stripe's message say which. The second form: when it connects, the integration couldn't read your Stripe account.Resolution: In the Stripe Dashboard, open Developers → API keys, choose the restricted key, choose Edit, and add the permission (the installation instructions list them all). Then resend the records the error log lists.
A setting can't be used
STRP-BIZL-1001 - API Url "{value}" is not Stripe's API address. Use https://api.stripe.com.
STRP-BIZL-1001 - These settings can't be used: {setting} "{value}": {what is allowed}.
Description: A setting holds a value the integration can't use, so the connection stops before any call to Stripe. The first form: API Url isn't an https address on Stripe's API host,
api.stripe.com(any other host, or an address that isn't https, is refused; a blank API Url meanshttps://api.stripe.com). The second form lists each optional setting with its value and what it allows (several are separated by;): Invoice Days Until Due takes a whole number of days from 1 to 365; Stripe Emails Invoices, Close Stripe Invoices Paid Elsewhere, Bring In Payment Link Sales, Bring In Subscription Invoices and Bring In Other Invoices take Yes or No (also True/False, Y/N, 1/0, On/Off); Skip Objects Marked In Metadata takes a Stripe metadata key of at most 40 characters, with no spaces or brackets.Resolution: Correct each listed setting on the subscription and save, or clear an optional setting to use its default. Set API Url back to
https://api.stripe.com.
Invoice FROM iPaaS.com (the Stripe invoice and its pay link)
These errors stop the transaction's Stripe invoice from being issued or changed, and nothing is sent to Stripe. The transaction gets no new Stripe Pay Link until the cause is fixed and the transaction is sent again (for example by a Manual Sync with its Transaction ID).
When a transaction that already has an open Stripe invoice changes and the change fails one of the checks in this section (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), the Stripe invoice already sent stays open at its old amount until the transaction is corrected and sent again. If it must not be paid meanwhile, cancel the transaction in iPaaS.com or void the invoice in Stripe.
The transaction has no number
STRP-VALD-1001 - The transaction has no TransactionNumber: map the transaction number to TransactionNumber.
Description: The transaction number becomes the Stripe invoice number the customer sees, so it is required. The Add/Update Stripe Invoice FROM iPaaS.com collection doesn't map it, or the transaction has none.
Resolution: Map the transaction number to TransactionNumber (the default template does), and make sure the system that sends the transaction gives it a number.
The iPaaS.com transaction id isn't mapped
STRP-VALD-1009 - Transaction {transaction number}: map the iPaaS.com transaction Id to IpaasTransactionId; it ties the Stripe invoice to the record.
Description: The iPaaS.com transaction id is kept on the Stripe invoice so its payments find their way back to this transaction. The collection doesn't map it.
Resolution: Map Id to IpaasTransactionId in Add/Update Stripe Invoice FROM iPaaS.com (the default template does).
The transaction number is too long
STRP-VALD-1005 - Transaction number "{transaction number}" is longer than 22 characters; Stripe invoice numbers allow 26, and a re-issue adds "-R1".
Description: Stripe invoice numbers are at most 26 characters (Stripe API reference, create an invoice: number, maximum length 26). When a transaction changes before it is paid, its Stripe invoice is re-issued with
-R1(then-R2and so on) added, so the transaction number itself can be at most 22 characters.Resolution: Use shorter transaction numbers, or map a shorter value to TransactionNumber.
The transaction has no email
STRP-VALD-1004 - Transaction {transaction number} has no valid customer email (it is blank or has no @): Stripe needs one to find the customer and to email the invoice. Map the customer's email to CustomerEmail, or correct it on the customer.
Description: The transaction has no valid email address. The integration finds or creates the Stripe customer by email, and Stripe emails the invoice there.
Resolution: Add the customer's email to the transaction in iPaaS.com (or in the system that sends it), or map the customer's email to CustomerEmail.
The currency isn't valid
STRP-VALD-1003 - Transaction {transaction number}: Currency "{value}" is not a 3-letter currency code (e.g. USD).
Description: The mapped currency isn't a 3-letter currency code.
Resolution: Map a 3-letter currency code (USD, EUR and so on) that your Stripe account accepts, or leave Currency blank to use your Stripe account's default currency.
Nothing to collect
STRP-VALD-1002 - Transaction {transaction number} has no amount to collect (Total must be more than 0).
Description: The transaction's Total is 0 or less and it has no Stripe invoice yet, so there is nothing for the customer to pay. A transaction that already has a Stripe invoice and whose Total drops to 0 doesn't get this error: its Stripe invoice is taken out of use instead, so the old pay link no longer asks for the old amount.
Resolution: Nothing to do for a zero or credit transaction. If these shouldn't be sent to Stripe at all, narrow the collection's filter.
The transaction has no lines
STRP-VALD-1010 - Transaction {transaction number} has no lines: map the Transaction Line FROM iPaaS.com collection (each line's description, quantity and price).
Description: The Stripe invoice shows each line of the transaction. The transaction has no lines, or the Add/Update Stripe Invoice Line FROM iPaaS.com collection isn't turned on or mapped.
Resolution: Turn on and map the Add/Update Stripe Invoice Line FROM iPaaS.com collection (the default template does).
A line can't be invoiced
STRP-VALD-1011 - Transaction {transaction number}, line {line}: no SKU or description for the customer to see.
STRP-VALD-1011 - Transaction {transaction number}, line {line} ({description}): map UnitPrice or ExtendedPrice.
STRP-VALD-1011 - Transaction {transaction number}, line {line} ({description}): the quantity can't be negative (a return belongs in a credit, not on the invoice).
STRP-VALD-1011 - Transaction {transaction number}, line {line} ({description}): map both PeriodStart and PeriodEnd, or neither (Stripe needs both ends of the period).
Description: A line has nothing for the customer to read (the first form), no price (the second form), a negative quantity (the third form), or only one end of its period mapped (the fourth form).
{line}counts the transaction's lines from 1.Resolution: Fix the line the message names, or its mapping in Add/Update Stripe Invoice Line FROM iPaaS.com. A returned item belongs on a credit in your invoicing system, not on the Stripe invoice. For the fourth form, map both PeriodStart and PeriodEnd, or neither.
The lines don't add up to the Total
STRP-VALD-1006 - Transaction {transaction number}: the lines plus tax and shipping less the discount come to {amount}, but the Total is {total}. Nothing was sent, so the customer is never asked for the wrong amount. Check the line prices (after line discounts) and the TaxAmount, ShippingAmount and DiscountAmount mappings.
STRP-VALD-1006 - Transaction {transaction number}: the lines plus shipping come to {amount} before the tax Stripe calculates, which is already more than the Total {total}. Nothing was sent, so the customer is never asked for the wrong amount. Check the line prices and the Total.
STRP-VALD-1006 - Transaction {transaction number}: the lines plus tax and shipping come to {amount} before the discounts Stripe takes off, which is already less than the Total {total}. Nothing was sent, so the customer is never asked for the wrong amount. Check the line prices and the Total.
STRP-VALD-1006 - Transaction {transaction number}: TaxAmount is mapped and Stripe is also asked to calculate the tax (AutomaticTax, or TaxRateIds on the transaction or a line), so the tax would be charged twice. Nothing was sent. Map one or the other: clear the TaxAmount mapping, or remove the Stripe tax mappings.
STRP-VALD-1006 - Transaction {transaction number}: DiscountAmount is mapped and Stripe is also asked to apply discounts (DiscountCodes on the transaction or a line), so the discount would be taken twice. Nothing was sent. Map one or the other: clear the DiscountAmount mapping, or remove the DiscountCodes mappings.
Description: The Stripe invoice is built from the lines, a Tax line, a Shipping line and a negative Discount line, and their sum must equal the transaction's Total to the cent (or the currency's smallest unit). It didn't, so nothing was sent. With tax or discounts that Stripe calculates (AutomaticTax, TaxRateIds or DiscountCodes mapped), the lines can't add up to the Total before Stripe calculates them: then only what can't be right is refused (the second and third forms: lines already above the Total before tax, or already below it before discounts), and Stripe's amount is checked against the Total when the invoice is made (STRP-BIZL-1017). The fourth and fifth forms: the transaction maps its own TaxAmount (or DiscountAmount) and also asks Stripe to calculate the tax (or apply discounts), which would charge the tax (or take the discount) twice.
Resolution: Compare the two amounts in the message. Check that each line's price is after its line discount, and that tax, shipping and the order-level discount are mapped (the discount as a positive amount). Or correct the transaction itself. Then resend it. For the fourth and fifth forms, map either the transaction's own TaxAmount or DiscountAmount, or Stripe's tax or discounts, never both.
A template placeholder wasn't replaced
STRP-VALD-1007 - Transaction {transaction number}: the {field} mapping still holds the template placeholder "{value}". Replace it in the FROM iPaaS.com mapping collection (or remove the mapping).
Description: A mapping still holds a
REPLACE with ...value from the default template. Placeholders are never sent to Stripe.Resolution: Replace the value in the mapping the message names, in Add/Update Stripe Invoice FROM iPaaS.com or Add/Update Stripe Invoice Line FROM iPaaS.com, or remove that mapping.
The due date isn't a date
STRP-VALD-1008 - Transaction {transaction number}: DueDate "{value}" is not a date.
Description: DueDate is mapped to something that isn't a date. DueDate is a day, such as
2026-11-15; a date with a time keeps only its date part.Resolution: Map a date to DueDate, or remove the DueDate mapping so the invoice is due after Invoice Days Until Due (default 30).
Stripe changed the amount
STRP-BIZL-1005 - Transaction {transaction number}: Stripe made invoice {invoice number} for {amount} instead of {total}, so it was voided before it was sent. Open the voided invoice in Stripe to see what changed the amount, correct it in Stripe, and send the transaction again.
Description: When Stripe finalized the invoice, it asked for a different amount than the transaction's Total. A customer balance or a customer discount is caught before the invoice is made (STRP-BIZL-1015), and Stripe's own tax or discounts mapped on the transaction are checked separately (STRP-BIZL-1017), so this error means something else in Stripe changed the amount. The integration voided the Stripe invoice at once, before it was sent to the customer.
Resolution: Open the voided invoice in Stripe to see what changed its amount, correct that in Stripe, then send the transaction again (a Manual Sync with its Transaction ID). The voided invoice's Stripe Invoice Status reads Void: here that means the integration voided it, not that the transaction was cancelled. Dismiss the error once it is fixed, so the platform doesn't retry it. If sending it again fails with STRP-EXTN-1004, raise it with your MiSP, then iPaaS.com Support.
Changed after Stripe took a payment or a credit note (warning)
STRP-BIZL-1003 - Transaction {transaction number} changed after Stripe received a payment or a credit note on invoice {invoice number}; a paid, part-paid or credited Stripe invoice can't be changed from iPaaS.com. Adjust it in Stripe (a credit note or refund).
STRP-BIZL-1003 - Transaction {transaction number} now totals 0, but Stripe invoice {invoice number} is {state}: a paid, part-paid or credited Stripe invoice can't be changed from iPaaS.com, so it was left as it is. Adjust it in Stripe (a credit note or refund).
Description: A warning, not a failure. The transaction changed after its Stripe invoice received a payment, or after a credit note was issued on it in Stripe, or its total went to 0 after that. Stripe can't change an invoice that has been paid or partly paid. A credit note is a change made in Stripe, so the integration keeps it: the invoice is not changed, voided or issued again. The change wasn't sent. The transaction's Stripe Message shows this warning too. An invoice marked uncollectible in Stripe is never changed either, but gives no warning unless it has a payment.
Resolution: Adjust the invoice in Stripe: issue a credit note, or refund the payment. For an uncollectible invoice, change or void it in Stripe.
Cancelled, but paid or credited in Stripe (warning)
STRP-BIZL-1004 - Transaction {transaction number} is cancelled in iPaaS.com, but Stripe invoice {invoice number} is {state}: it was left as it is. Refund it in Stripe if needed.
STRP-BIZL-1004 - Transaction {transaction number} is cancelled in iPaaS.com, but Stripe invoice {invoice number} is {state}: it was left as it is. Void it in Stripe if the customer shouldn't pay the rest.
Description: A warning, not a failure. The transaction was cancelled in iPaaS.com, but its Stripe invoice is paid, part paid, reduced by a credit note or marked uncollectible, so it wasn't voided. The message says which (for example "open with a credit note" or "part paid with a payment"). The transaction's Stripe Message shows this warning. An invoice that is already void gives no warning.
Resolution: If the customer should get the money back, refund the payment in Stripe. The refund then arrives on the transaction as a negative payment. An invoice with a credit note and no payment can be voided in Stripe if the customer shouldn't pay the rest. An uncollectible invoice with no payment can be voided in Stripe.
Part paid outside Stripe (warning)
STRP-BIZL-1006 - Transaction {transaction number} was part paid outside Stripe: {balance} is still owed, but Stripe invoice {invoice number} still asks for {amount}. The integration doesn't lower an issued invoice for a payment made elsewhere: issue a credit note on it in Stripe, or tell the customer the amount still owed, and record the rest in iPaaS.com when it arrives; at a zero balance the Stripe invoice is closed as paid elsewhere.
Description: A warning, not a failure. Part of the transaction was paid outside Stripe (for example by cheque) after its Stripe invoice was issued, and some is still owed. The integration doesn't record a part payment made elsewhere on an invoice already issued, so it still asks for the amount it was issued for. (A payment made before the invoice was issued is shown on it as Payment already received, and the invoice asks only for the rest.) The transaction's Stripe Message shows this warning too. (When the transaction is paid in full outside Stripe, see STRP-BIZL-1010 below.)
Resolution: Tell the customer the amount still owed, and record the rest in iPaaS.com when it arrives: once the balance reaches 0, the Stripe invoice is marked paid outside Stripe (with Close Stripe Invoices Paid Elsewhere at
Yes, the default). To lower the invoice to the balance, issue a credit note on it in Stripe. Don't void the Stripe invoice in Stripe to get a new one: an invoice voided in Stripe isn't issued again (STRP-BIZL-1014).
Paid in full outside Stripe, but the close-out setting is off (warning)
STRP-BIZL-1010 - Transaction {transaction number} is paid in full outside Stripe, but Close Stripe Invoices Paid Elsewhere is off, so Stripe invoice {invoice number} still asks for {amount}. Mark it paid or void it in Stripe, or turn the setting on.
Description: A warning, not a failure. The transaction was paid in full outside Stripe (for example by cheque or bank transfer recorded in your own system), but the subscription's Close Stripe Invoices Paid Elsewhere setting is
No, so the integration left the open Stripe invoice as it is. It still asks the customer for the amount. The transaction's Stripe Message shows this warning too.Resolution: In the Stripe Dashboard, mark the invoice paid (paid outside Stripe) or void it. Or, if the integration should close such invoices, set Close Stripe Invoices Paid Elsewhere to
Yesand send the transaction again.
Voided in Stripe (warning)
STRP-BIZL-1014 - Transaction {transaction number}: Stripe invoice {invoice number} was voided in Stripe, so iPaaS.com doesn't issue it again. To bill this transaction again, clear its Stripe Invoice ID field and save it; to stop billing it, cancel it.
Description: A warning, not a failure. Someone voided the transaction's Stripe invoice in Stripe (in the Stripe Dashboard, for example). That is a decision made in Stripe, so the integration keeps it: a later change to the transaction doesn't issue a new invoice. The transaction's Stripe Message shows this warning. Voids the integration makes itself (a re-issue or a cancel, for example) never give this warning.
Resolution: Decide in iPaaS.com. To bill the transaction again, clear its Stripe Invoice ID custom field and save the transaction: a new Stripe invoice is issued. To stop billing it, cancel the transaction. Sending it again unchanged changes nothing.
Two or more live Stripe invoices for one transaction
STRP-BIZL-1013 - Transaction {transaction number} has {count} Stripe invoices still open or paid ({invoice number and id, ...}), so the customer could be asked to pay more than once. Void the one that shouldn't be there in the Stripe Dashboard (never one that's paid), then retry this transfer.
Description: The integration found two or more Stripe invoices for the transaction that are still open or paid. It looks at every invoice of the transaction, whether or not the transaction already has a Stripe Invoice ID. It doesn't guess which one is right, so nothing was sent. This can happen when a second subscription or another system issued an invoice for the same transaction. Deleting the transaction in iPaaS.com can give this error too.
Resolution: In the Stripe Dashboard, find the invoices the message names. Void the one that shouldn't be there. Never void one that's paid. Then retry the transfer from the error list. If one transaction keeps getting two invoices, check for a second subscription.
The Stripe customer's balance or discount would change the amount
STRP-BIZL-1015 - Transaction {transaction number}: Stripe customer {Stripe customer id} has a balance of {amount} {in credit or owed}, which Stripe would apply to the invoice and change its amount. No invoice was made. Clear the customer's balance in Stripe (Customers, the customer, Balance), then send the transaction again.
Description: Before it makes an invoice, the integration checks the Stripe customer. A balance (a credit, or an amount owed) in the invoice's currency, or a discount on the customer, would make Stripe ask for a different amount than the transaction's Total. Nothing was made in Stripe, and a retry makes nothing either until the balance or discount is gone.
Resolution: In the Stripe Dashboard, open the customer the message names. Clear the balance (or remove the discount). Then send the transaction again (a Manual Sync with its Transaction ID), or let the platform retry it.
Stripe kept answering with a void invoice or a taken number
STRP-BIZL-1016 - Transaction {transaction number}: Stripe answered five times in a row with an invoice that is void or a number that is taken (last {invoice number}), so no invoice was issued and no line was added. Retry this transfer; if it fails again, look in Stripe for this transaction's invoices and void the one in the way.
Description: The integration tried five invoice numbers for the transaction (the number, then -R1, -R2 and so on), and each time Stripe answered with an invoice that is already void, or said the number was taken by an earlier invoice of the transaction. It stopped without adding anything, so no void invoice gets lines.
Resolution: Retry the transfer from the error list. If it fails again, search Stripe's invoices for the transaction number: void any draft or open invoice of the transaction that shouldn't be there, then retry. If it still fails, raise it with your MiSP, then iPaaS.com Support.
Stripe's tax or discounts came to another amount
STRP-BIZL-1017 - Transaction {transaction number}: with the {tax, discounts, or tax and discounts} Stripe calculates, Stripe made invoice {invoice number} for {amount}, but the transaction's Total is {total}. It was voided before it was sent, so the customer is never asked for an amount nobody set, and the unchanged transaction makes no new invoice for 24 hours. Make the Total match what Stripe calculates (check the tax rates, tax codes and discounts mapped), or map TaxAmount and DiscountAmount instead of Stripe's, then send the transaction again.
Description: The transaction maps tax or discounts that Stripe calculates (AutomaticTax, TaxRateIds or DiscountCodes, on the transaction or a line). When Stripe finalized the invoice, the amount it calculated wasn't the transaction's Total. The integration voided the Stripe invoice at once, before it was sent to the customer, so nobody is asked for an amount iPaaS.com didn't set. A retry of the unchanged transaction, the platform's own retries included, gives this error again without making another invoice for 24 hours from the void. After that, one retry asks Stripe again, so a fix made only in Stripe (its tax settings) is picked up.
Resolution: Compare the two amounts in the message. Either correct the Total in iPaaS.com so it matches the tax and discounts Stripe calculates (check the tax rates, tax codes, whether prices include tax, and the discount codes mapped), or stop asking Stripe to calculate them: remove the AutomaticTax, TaxRateIds and DiscountCodes mappings and map TaxAmount and DiscountAmount instead. Then send the transaction again (a Manual Sync with its Transaction ID). The voided invoice's Stripe Invoice Status reads Void: here that means the integration voided it, not that the transaction was cancelled.
Memo, name or phone changed after the invoice was issued (warning)
STRP-BIZL-1018 - Transaction {transaction number}: {Memo, Customer Name and Customer Phone (those that changed)} changed after Stripe invoice {invoice number} was issued. Stripe keeps an issued invoice's memo, customer name and phone, so it still shows the old details. For the new details, update the customer in Stripe (name or phone), void the invoice in Stripe, then clear the Stripe Invoice ID and save the transaction.
Description: A warning, not a failure. The transaction's Memo, Customer Name or Customer Phone changed in iPaaS.com after its Stripe invoice was issued. Stripe doesn't let an issued (finalized) invoice's memo, customer name or phone change (Stripe API reference, update an invoice: "Once an invoice is finalized, you can no longer change most of its details"), so the change wasn't sent and the invoice keeps what it was issued with. The warning shows in the transaction's Stripe Message until the fields match the invoice again or a new invoice is issued. The memo is compared with the invoice's memo; the name and phone with what was sent when the invoice was issued.
Resolution: If the issued invoice is fine as it is, no action is needed; to clear the warning, put the fields back as they were. If the customer needs an invoice with the new details before paying: for a name or phone, update the customer in Stripe first (the invoice takes them from the Stripe customer); then void the invoice in Stripe, clear the transaction's Stripe Invoice ID custom field and save the transaction, and a new invoice is issued (Known Limitations 6).
A deleted transaction's invoice isn't found yet
STRP-NFND-1002 - Transaction {transaction number} was deleted, but Stripe's invoice search doesn't show its invoice yet (it can trail a new invoice by a minute). Retry this transfer; if it still fails, void the invoice in Stripe.
Description: A transaction was deleted in iPaaS.com seconds after its Stripe invoice was issued, and Stripe's invoice search didn't list the invoice yet (it can trail a new invoice by up to a minute), so the open invoice wasn't voided.
Resolution: Retry the transfer from the error list; if it fails again, void the invoice in the Stripe Dashboard.
Customers FROM iPaaS.com and TO iPaaS.com
The customer has no email
STRP-VALD-1004 - Customer {customer}: no valid email (it is blank or has no @). Stripe customers are matched by email; map the customer's email to Email, or correct it on the customer (the template's filter skips customers without one).
Description: A customer sent FROM iPaaS.com has no email. Stripe customers are found by email.
Resolution: Add the customer's email in iPaaS.com, or map it to Email in Add/Update Stripe Customer FROM iPaaS.com.
A template placeholder wasn't replaced
STRP-VALD-1007 - Customer {email}: the {field} mapping still holds the template placeholder "{value}". Replace it in the Customer FROM iPaaS.com mapping collection.
Description: A customer mapping still holds a
REPLACE with ...value. Placeholders are never sent to Stripe.Resolution: Replace the value in the mapping the message names, in Add/Update Stripe Customer FROM iPaaS.com.
A customer value Stripe can't accept
STRP-VALD-1012 - Customer {email}: the {billing|shipping} address country "{value}" is not a 2-letter country code, so nothing was sent to Stripe. Stripe accepts only ISO 3166-1 two-letter codes (US, CA, GB). Map a 2-letter code to the address Country (a translation collection can turn country names into codes), or correct the address.
STRP-VALD-1012 - Customer {email}: {Balance or NextInvoiceSequence} is {value}, but Stripe takes a whole number there, so nothing was sent to Stripe. {how to correct the mapping}
STRP-VALD-1012 - Customer {email}: the tax ID "{entry}" in TaxIdData is not type:value (for example eu_vat:DE123456789), so nothing was sent to Stripe. Correct the TaxIdData mapping.
Description: The customer has a value Stripe would refuse or this integration can't send: an address country that isn't a 2-letter code, a Balance or NextInvoiceSequence that isn't a whole number (Stripe takes whole numbers; Balance is in the smallest currency unit, such as cents), or a TaxIdData entry without a type and a value. It is checked before anything is sent, so nothing is half written.
Resolution: Correct the value the message names, in the customer or in the Add/Update Stripe Customer FROM iPaaS.com mapping (a translation collection can turn country names into 2-letter codes), then resend the customer.
Customer deletes aren't sent
STRP-BIZL-1008 - Stripe customers aren't deleted from iPaaS.com: a deleted Stripe customer loses its invoices and payment history. Turn off or remove the customer Delete collection.
Description: A delete reached the Stripe customers. Add/Update Stripe Customer FROM iPaaS.com offers no Delete, so this appears only if a delete mapping or collection for customers was added anyway. Deleting a Stripe customer would lose its invoices and payment history, so the integration never does it.
Resolution: Remove the delete mapping or collection for customers. Manage Stripe customers you no longer need in Stripe.
The email already belongs to another Stripe customer
STRP-BIZL-1009 - Stripe customer {Stripe customer id} has the email {email}, which iPaaS.com customer {id} already has, linked to Stripe customer {other Stripe customer id}. Stripe can't merge customers: merge their records in Stripe, or give this one its own email. Nothing was transferred.
STRP-BIZL-1009 - Stripe customer {Stripe customer id}: {count} iPaaS.com customers have the email {email}, so it can't be matched to one; nothing was transferred.
Description: An error, shown in the error list. iPaaS.com allows one customer per email. A Stripe customer arriving TO iPaaS.com is linked first to the iPaaS.com customer it was created for (when the integration created it, it keeps that customer's iPaaS.com id), then to the one iPaaS.com customer with the same email. Here its email belongs to an iPaaS.com customer already linked to a different Stripe customer (the first form), or to several iPaaS.com customers (the second form), so it can't be linked and nothing is transferred. When this happens while a Stripe-made sale brings its customer in first, the sale arrives without the integration's customer link; iPaaS.com may still link it to the iPaaS.com customer with the buyer's email.
Resolution: For the first form, merge the two customers' records in Stripe, or give this one its own email. For the second, the duplicates are in iPaaS.com, so merging in Stripe changes nothing: decide which iPaaS.com customer keeps the email (merge or change the others in iPaaS.com), then resync the Stripe customer.
Two or more Stripe customers can't be told apart
STRP-BIZL-1012 - {count} Stripe customers have the email {email} ({Stripe customer ids}) and none of them is linked to {an iPaaS.com customer, or iPaaS.com customer id}, so it can't be matched to one; nothing was sent. Stripe can't merge customers: delete or re-email the extra ones in the Stripe Dashboard, then retry this transfer.
STRP-BIZL-1012 - {count} Stripe customers with the email {email} are marked as iPaaS.com customer {id} ({Stripe customer ids}), so it can't be matched to one; nothing was sent. Stripe can't merge customers: delete or re-email the extra ones in the Stripe Dashboard, then retry this transfer.
STRP-BIZL-1012 - {count} Stripe customers are marked as iPaaS.com customer {id} ({Stripe customer ids}), so it can't be matched to one; nothing was sent. Stripe can't merge customers: delete the extra ones in the Stripe Dashboard, then retry this transfer.
Description: A customer sent FROM iPaaS.com, or the customer of a transaction being invoiced, matches two or more Stripe customers, and the integration doesn't guess which one is right. Nothing was sent: no Stripe customer and no invoice is made, and a Stripe invoice already sent stays as it was. The integration finds the Stripe customer in this order: its Stripe Customer ID; then the Stripe customer marked as this iPaaS.com customer; then by exact email, taking the one marked as this iPaaS.com customer, or else the only one with the email that is marked as nobody's. When none matches, a new Stripe customer is made. A Stripe customer marked as another iPaaS.com customer is never taken, because two iPaaS.com customers can share an email.
Resolution: In the Stripe Dashboard, open the Stripe customers the message names. Delete the extra ones, or give them their own email. Then retry the transfer from the error list.
Webhooks, write-back and the poll
The Stripe invoice couldn't be written back yet (warning)
STRP-INTL-1003 - Stripe invoice {Stripe invoice id} couldn't be written back onto the iPaaS.com transaction ({reason}). Its invoice webhook or the next poll writes it; or send the transaction FROM iPaaS.com again.
Description: A warning in iPaaS.com's company log, never in the error list, and not a failure: on the record, the transaction's Stripe Invoice ID, Stripe Pay Link and Stripe Invoice Status stay empty although the Stripe invoice exists. Right after it issues, re-issues, voids or closes a Stripe invoice, the integration starts a transfer TO iPaaS.com that writes Stripe Invoice ID, Stripe Pay Link and Stripe Invoice Status onto the transaction. That transfer couldn't be started or reported errors. The Stripe invoice itself was issued.
Resolution: Usually nothing: the invoice's next webhook, or the next run of the
invoice.pollpoll event (if you created it), writes the fields. If they stay empty, run a Manual Sync TO iPaaS.com with the Stripe invoice id the message names (in_…; search it in the Stripe Dashboard) or the transaction number, or send the transaction FROM iPaaS.com again.
The webhook address or key wasn't supplied
STRP-INTL-1004 - iPaaS.com didn't supply this subscription's webhook address (IPaaSApi_WebhookUrl).
STRP-INTL-1004 - iPaaS.com didn't supply this subscription's webhook key (WebhookApiKey).
STRP-INTL-1004 - iPaaS.com didn't supply this subscription's id.
Description: The names in brackets are iPaaS.com's own names for the subscription's webhook address and webhook key. When a webhook is turned on, the integration registers a webhook endpoint for your subscription in your Stripe account, pointing at your subscription's iPaaS.com webhook address. iPaaS.com didn't hand the integration that address, the subscription's webhook key or its id, so the endpoint couldn't be set up.
Resolution: Check that the subscription has a webhook key, then turn the Stripe event on again. If it repeats, raise it with your MiSP, then iPaaS.com Support.
The Stripe webhook couldn't be turned on or off
STRP-EXTN-1005 - The Stripe webhook for {event} couldn't be turned {on or off}: {reason}
STRP-EXTN-1005 - The Stripe webhook for {event} couldn't be turned {on or off}: {reason}{advice} Records still arrive by the invoice.poll and customer.poll schedules.
Description: An error. The webhook endpoint couldn't be created or changed.
{reason}quotes the underlying error, which may carry its own code: STRP-INTL-1004 (iPaaS.com didn't supply the webhook address or key), a STRP-AUTH- or STRP-BIZL-1001 code (the key or a setting was refused), Stripe's refusal, most often because a restricted key doesn't have the Webhook Endpoints (write) permission, or Stripe's webhook endpoint changing while other events were turned on or off at the same moment (the reason then says to turn the event off and on again); then{advice}reads " A restricted key needs the Webhook Endpoints (write) permission."Resolution: Read the code inside the message. STRP-INTL-1004 inside: see that error above. A STRP-AUTH- or STRP-BIZL-1001 code inside: fix the key or setting it names. If the reason says the endpoint kept changing, turn the event off and on again. Otherwise add Webhook Endpoints (write) to the restricted key in Stripe (Developers → API keys, the key, Edit), then turn the event on again. Meanwhile, records still arrive through the
invoice.pollandcustomer.pollpoll events, if they are scheduled (subscribing creates none).
The poll gap is longer than Stripe keeps events (warning)
STRP-BIZL-1002 - The last Stripe events poll ({poll}) was more than {days} days ago; Stripe keeps events about 30 days, so anything older can't be read. Resync the records changed in that gap.
Description: A warning in iPaaS.com's company log, not in the error list, and not a failure. The poll reads Stripe's events since its last run, and Stripe keeps events for 30 days (Stripe API reference, list all events: "going back up to 30 days"). The poll hadn't run for longer than that (for example its poll event was turned off), so changes older than about 30 days can't be read.
Resolution: Resync the transactions and customers that changed in Stripe during the gap (a Manual Sync TO iPaaS.com with each Stripe id). Keep the poll events scheduled.
Any flow
Stripe answered with an unexpected status
STRP-EXTN-1001 - Stripe answered {HTTP status} {status name} to {action}: {Stripe's message}
Description: Stripe answered with an HTTP status the integration doesn't expect for that call (not 400, 401, 402, 403, 404, 409, 424, 429, a 5xx or no answer, which have their own codes). Stripe's own message is quoted.
Resolution: Retry the transfer. If it repeats, send the message to your MiSP, then iPaaS.com Support.
Stripe is temporarily unavailable
STRP-EXTN-1002 - Stripe couldn't complete {action} right now ({reason}). The transfer will be retried.
STRP-EXTN-1002 - Stripe couldn't complete {action} right now ({reason}: {Stripe's message}). The transfer will be retried.
Description: Stripe answered with a server error (5xx), a temporary conflict (409, for example two changes to the same record at once), a 424 (a service Stripe depends on failed), or didn't answer at all; {reason} gives the status or the connection error, and for a 409 or 424 Stripe's own message is quoted.
Resolution: Usually none: iPaaS.com retries the transfer. Don't change the settings. If it lasts, check Stripe's status at status.stripe.com. If the record is still in the error log once Stripe answers again, resend it. Payments and customers missed in the meantime are also picked up by the poll.
Stripe's rate limit was reached
STRP-EXTN-1003 - Stripe rate limit reached during {action}; retrying after {seconds}s.
STRP-EXTN-1003 - Stripe rate limit reached during {action}; retrying after {seconds}s (rate limited {count} times in a row: each wait doubles, up to {maximum}s).
Description: Stripe answered HTTP 429: too many requests at once. iPaaS.com holds the transfer for the time Stripe asks for (Retry-After); when Stripe doesn't say, the wait starts at about 2 seconds and doubles with each 429 in a row, with a little randomness, up to 60 seconds.
Resolution: None: iPaaS.com holds the transfer and retries it. If this error is frequent, lower the subscription's Concurrent Connections.
Stripe has no such record
STRP-NFND-1001 - Stripe has no record for {action} (404): {Stripe's message}
Description: Stripe answered HTTP 404 to the connection check or to a change the integration sent. Most often API Url has a path after
https://api.stripe.com, so every call misses (the transfer then shows "Unable to connect to subscription"). A Stripe record that no longer exists when the integration reads it by its id isn't an error: that record is simply skipped, and a Stripe invoice deleted in Stripe is issued again on the next send of its transaction.Resolution: Set API Url to
https://api.stripe.com, with nothing after it. Otherwise send the record again.
Stripe refused the request
STRP-EXTN-1004 - Stripe refused {action}: {Stripe's message}
Description: Stripe answered HTTP 400 or 402, or a 409 for a reused request key (idempotency_error): for example the invoice is already closed in Stripe, or a value isn't one Stripe accepts. Stripe's reason is quoted. Any Stripe key in Stripe's message is replaced by [redacted].
Resolution: Act on Stripe's reason in the message: correct the record or the setting it names, then resync.
A collection added on its own for a record that moves with its parent
STRP-BIZL-1011 - This record moves with its transaction or customer, never on its own: remove this collection, and send the transaction or customer instead.
Description: A mapping collection was added on its own for a record that moves with its transaction or customer, for example a payment, address or line FROM iPaaS.com, and a transfer (a webhook, a poll or a Manual Sync) reached it. Lines, addresses and payments move only inside the template's parent collections.
Resolution: Remove that collection from the subscription. To send the record, send its transaction or customer instead.
A data type the integration doesn't support
STRP-BIZL-1007 - The Stripe integration has no {data type} data (mapping collection type {number}): it supports Transaction (with lines, addresses and payments) and Customer (with addresses). Remove or turn off this mapping collection.
Description: The subscription has a mapping collection of a data type the Stripe integration doesn't handle, for example a Product collection, and a transfer reached it.
Resolution: Remove or turn off the named mapping collection. Keep the Stripe template collections.
iPaaS.com couldn't complete a lookup
STRP-INTL-1002 - iPaaS.com could not complete {action} (HTTP {status}). Retry the transfer; if it repeats, contact iPaaS.com support with the transfer's details.
STRP-INTL-1002 - iPaaS.com could not complete {action} (HTTP {status}, iPaaS.com error {iPaaS.com code}). Retry the transfer; if it repeats, contact iPaaS.com support with the transfer's details.
Description: One of the integration's own calls to iPaaS.com failed: looking up or linking an external id, or reading a customer or transaction it needs. When iPaaS.com answered with its own error code, the message names it (for example
VALD-1023); look that code up in the iPaaS.com Help Center. The rest of the answer is kept in the technical log.Resolution: Retry the transfer. If it repeats, raise it with your MiSP, then iPaaS.com Support, with the transfer's details.
The platform sent no record
STRP-INTL-1001 - The platform asked the Stripe integration to transfer a record but sent none (mapping collection type {type}). Retry the transfer; if it repeats, contact iPaaS.com support.
Description: The platform asked the integration to read, create, update, delete or poll without a record. It isn't caused by a mapping or a setting.
Resolution: Retry the transfer. If it repeats, raise it with your MiSP, then iPaaS.com Support, with the transfer's details.
