Summary
The Add QuickBooks Online Payment Method FROM iPaaS.com mapping collection creates iPaaS.com payment methods in QuickBooks Online by name, so that the payments and sales receipts iPaaS.com sends to QuickBooks can use them. A method that QuickBooks does not have yet is created with the iPaaS.com name and with the QuickBooks type CREDIT_CARD when its iPaaS.com payment type is Credit Card, otherwise NON_CREDIT_CARD.
Although the collection is named Add, its sync type is Add/Update: an iPaaS.com payment method already linked to a QuickBooks method updates that QuickBooks method when it changes in iPaaS.com, and the update writes the iPaaS.com name to QuickBooks. Before a method that is not linked yet is created, the integration looks for a QuickBooks payment method with the same name, active or inactive, and the collection's Collision Handling Method decides what happens when one exists.
ID Format
Manual Sync ID: the iPaaS.com payment method id, for example 100066.
External ID saved after sync: the QuickBooks payment method id, for example 5. After a successful create, or a link made by collision handling, iPaaS.com keeps it in an external-ID record for this subscription that links the iPaaS.com payment method to its QuickBooks method, so later transfers of the same method update that QuickBooks method instead of creating another.
Deleted Record Support
Not supported. QuickBooks payment methods cannot be deleted, and the paymentmethod/deleted scope is not supported, so do not turn it on. Deleting a payment method in iPaaS.com does not remove it from QuickBooks; to stop using a method, make it inactive in QuickBooks.
Mapping Collection Status
Status: Enabled.
Trigger events: the iPaaS.com paymentmethod/created and paymentmethod/updated scopes, once turned on under Outbound Data Flows. Whether a transfer creates or updates the QuickBooks method depends on whether the iPaaS.com method is already linked by its external ID, not on which of the two scopes fired.
Duplicate or Conflicting Mappings
Add/Update QuickBooks Online Payment Method TO iPaaS.com brings QuickBooks payment methods into iPaaS.com, in the opposite direction. Running both directions is supported: a method this collection has just written to QuickBooks is not sent straight back on the next poll, and the TO iPaaS.com collection keeps iPaaS.com names and descriptions when it updates.
Important: This collection overwrites QuickBooks payment methods. Each update writes the iPaaS.com name to the linked QuickBooks method, so a QuickBooks method linked to a differently named iPaaS.com method (for example QuickBooks Visa linked to iPaaS.com VISA, by hand or by the same-name link that Add/Update QuickBooks Online Payment Method TO iPaaS.com makes) is renamed to the iPaaS.com name. The payment-method translations match QuickBooks names, so keep them in step with any rename. Decide whether iPaaS.com or QuickBooks owns payment method names before turning on paymentmethod/updated.
Collision handling. The Collision Handling Method setting is on this mapping collection's settings in iPaaS.com. It decides what happens when a create finds a QuickBooks payment method, active or inactive, with the same name. Matching is by name only. The default template ships with no collision setting, which behaves as Error. Choose a method before going live:
Error: the transfer fails with QBOL-BIZL-1003, naming the existing QuickBooks method's id and name. Nothing is created and nothing is linked.
Remap and Link: the existing QuickBooks method is linked to the iPaaS.com method instead of creating a duplicate. iPaaS.com then updates the linked QuickBooks method with the mapped name and type.
Update and Link: the existing QuickBooks method is linked and updated with the mapped values (for example a NON_CREDIT_CARD method becomes CREDIT_CARD when the iPaaS.com method is a credit card).
Update and No Link: the existing QuickBooks method is updated but no link is saved, so every later transfer matches it by name again. Validate this method in a staging environment before relying on it in production.
Both link methods rewrite the matched QuickBooks method. Use Error if QuickBooks must stay the owner of its existing methods.
Supported Child Collections
None.
System Caveats
QuickBooks Online Caveats
Name rules: QuickBooks payment method names must be unique, and QuickBooks allows at most 31 characters. Keep iPaaS.com payment method names that reach QuickBooks within that length.
Two types only: QuickBooks records only whether a method is a credit card: CREDIT_CARD or NON_CREDIT_CARD. Gift card, debit card, EBT, cash and check methods all become NON_CREDIT_CARD.
No delete: QuickBooks payment methods cannot be deleted, only made inactive.
Inactive methods are matched: the name match before a create includes inactive QuickBooks methods. This collection does not map Active, so a linked inactive method stays inactive; make it active in QuickBooks if payments are to use it.
Rate limits: QuickBooks allows 500 requests a minute and 10 a second per company. If the limit is reached, iPaaS.com holds the transfer and retries it automatically after a minute. If rate-limit errors continue for hours, QuickBooks' monthly limit for the iPaaS.com app may have been reached: contact your MiSP or iPaaS.com Support (see QuickBooks Online Known Limitations).
iPaaS.com Caveats
Sparse updates: an update sends only the fields that carry a value. A blank type is not sent, so the QuickBooks type stays as it is.
Translations for transactions: creating a method in QuickBooks does not add it to the payment-method translations. Add a row for it to the translation used by the payment and sales receipt collections (see Payment Method Translation Values below).
Stale link: when the linked QuickBooks method no longer exists, the update fails with QBOL-NFND-1003. Remove the stale link in iPaaS.com and send the method again.
Errors and retries: iPaaS.com retries every errored transfer automatically on a growing schedule, so a collision error repeats until the Collision Handling Method is set or the name is changed.
Prerequisite Handling
None. A payment method depends on no other record.
Setup Requirements
iPaaS.com Configuration
Automatic transfers do not start by themselves. In the subscription configuration, open Outbound Data Flows and turn on the iPaaS.com scopes paymentmethod/created and paymentmethod/updated. Until they are turned on, no payment methods are sent to QuickBooks. Do not turn on paymentmethod/deleted.
Before going live, choose the collection's Collision Handling Method (see Duplicate or Conflicting Mappings), and decide which system owns payment method names before turning on paymentmethod/updated.
Initialization is not supported. Payment methods that already exist in iPaaS.com are not sent until they change; to send one now, transfer it with Manual Sync.
QuickBooks Online Configuration
Nothing beyond the connection. QuickBooks' standard methods (Cash, Check, Visa, MasterCard, Discover) already exist in a new QuickBooks company, so an iPaaS.com method with one of those names finds the QuickBooks method and follows the Collision Handling Method instead of creating a new one. The iPaaS.com methods the default translations use differ from them in letter case (iPaaS.com VISA, QuickBooks Visa). QuickBooks compares names in its queries without regard to letter case (Intuit: Query operations and syntax, checked October 2026), so iPaaS.com VISA finds QuickBooks Visa.
Integration Flow
An iPaaS.com payment method is created or updated and the paymentmethod/created or paymentmethod/updated scope fires, or a method is sent with Manual Sync.
The filter keeps only methods that have a Name.
The mappings set the QuickBooks name and, through the type translation, the QuickBooks type.
If the method is already linked, the integration updates the linked QuickBooks method with the mapped name, and with the type only when the translation supplies one.
If the method is not linked yet, a blank name fails with QBOL-VALD-1003. Otherwise the integration looks for a QuickBooks payment method with the same name, active or inactive.
When one exists, the Collision Handling Method decides (see Duplicate or Conflicting Mappings). When none exists, the QuickBooks payment method is created with the mapped name and type (NON_CREDIT_CARD when the type is blank), and its QuickBooks id is saved as the external ID.
Mappings
Add QuickBooks Online Payment Method FROM iPaaS.com
iPaaS.com data type: Payment Method
Mapping Filter
// Every payment method with a name. return Name != null;
Filter Description. Every iPaaS.com payment method that has a Name is processed. Methods without a name are skipped without an error. A name that is empty text passes the filter, and a create then fails with QBOL-VALD-1003.
Mapping Type | Source Field (iPaaS.com) | Destination Field (QuickBooks Online) | Description |
Field | Name | Name | Required. The iPaaS.com payment method name becomes the QuickBooks name, for example Gift Card, and is how an existing QuickBooks method is found before a create. On an update of a linked method this name is written to QuickBooks, renaming a differently named QuickBooks method; keep the payment-method translations in step with any rename. |
Translation | PaymentType (translation QuickBooks Online Payment Method Type FROM iPaaS.com) | Type | Recommended. Translates the iPaaS.com payment type into CREDIT_CARD or NON_CREDIT_CARD. A type with no translation row arrives blank: a new method is created as NON_CREDIT_CARD, and an update leaves the QuickBooks type as it is. Without this mapping every method is created as a non-credit-card method. |
Payment Method Type Translation Values
The Type mapping uses the translation QuickBooks Online Payment Method Type FROM iPaaS.com, which ships with one row:
iPaaS.com payment type | QuickBooks type |
Credit Card | CREDIT_CARD |
Every other iPaaS.com payment type (for example Cash, Check, Gift Card or EBT) has no row and arrives blank. QuickBooks accepts only CREDIT_CARD and NON_CREDIT_CARD, so do not add rows that pass other values through (such as Cash to Cash).
Payment Method Translation Values
The QuickBooks names this collection creates are the values on the QuickBooks side of the translation QuickBooks Online Payment Method FROM iPaaS.com, used by Add QuickBooks Online Payment FROM iPaaS.com and Add QuickBooks Online Sales Receipt Payment FROM iPaaS.com. The translation ships with these rows:
iPaaS.com payment method | QuickBooks payment method |
VISA | Visa |
DISCOVER | Discover |
AMEX | American Express |
MASTERCARD | MasterCard |
CASH | Cash |
CHECK | Check |
CreditCard-Visa | Visa |
CRCARD | Visa |
Add a row for every other iPaaS.com method your payments use (for example Gift Card), pointing at the QuickBooks method this collection created. A payment whose method has no row fails with QBOL-NFND-1007.
Error Handling
Errors appear in Dashboard / Integration Monitoring / Error Logs, and iPaaS.com retries an errored transfer automatically on a growing schedule. Error messages that come from QuickBooks are explained in QuickBooks Online Error Messages.
QBOL-VALD-1003 - A QuickBooks payment method needs a name. The method's name is empty. Give the iPaaS.com payment method a name and send it again.
QBOL-BIZL-1003 - QuickBooks already has payment method {id} '{name}'. Link it, or set the collection's collision handling to Remap and Link. A QuickBooks method, active or inactive, already has this name and the Collision Handling Method is not set. Set it (see Duplicate or Conflicting Mappings), or rename the iPaaS.com method.
QBOL-VALD-1004 - Cannot update a QuickBooks payment method without its id (got '{value}'). The external ID saved for the method is not a QuickBooks payment method id. Correct or remove the link in iPaaS.com and send the method again.
QBOL-NFND-1003: the linked QuickBooks method no longer exists. Remove the stale link in iPaaS.com and send the method again.
QBOL-EXTN-1010: QuickBooks refused a duplicate name, for example an update that renames the method to a name another QuickBooks method already has.
QBOL-EXTN-1007: QuickBooks refused a value as too long, for example a name over 31 characters.
QBOL-EXTN-1013: QuickBooks limited the request rate; iPaaS.com retries after a minute.
Connection errors (QBOL-AUTH codes) are covered in QuickBooks Online Error Messages.
Testing & Validation
Create an iPaaS.com payment method Gift Card with payment type Gift Card, and send it with Manual Sync. Confirm QuickBooks has a payment method Gift Card of type NON_CREDIT_CARD.
Create an iPaaS.com payment method with payment type Credit Card and send it. Confirm the QuickBooks method has type CREDIT_CARD.
With no Collision Handling Method set, send an iPaaS.com method named Check. Confirm the transfer fails with QBOL-BIZL-1003 and no second Check is created. Set Remap and Link, send it again, and confirm the existing QuickBooks Check is linked.
With paymentmethod/updated turned on, rename the Gift Card method in iPaaS.com. Confirm the linked QuickBooks method is renamed, and update the payment-method translation row to match.
Additional Notes
Out of scope: deleting payment methods (QuickBooks has no delete, and paymentmethod/deleted is not supported); making QuickBooks methods inactive or active (this collection does not map Active).
Known limitations: a create first matches an existing QuickBooks method by name, and payment methods have no delete. See QuickBooks Online Known Limitations.
Related Documents
Related Mapping Documentation