Contents
Summary
A BigCommerce deposit ticket is transferred to iPaaS.com as a Transaction record. A deposit ticket is a special clone of a BigCommerce order: when an order qualifies for deposit-ticket handling, BigCommerce produces a clone whose ID ends in -D, and this family of collections processes that -D clone. The ticket represents the non-gift-card sales portion of the order and is designed to be sent downstream to an ERP or accounting system. The ticket header — buyer, totals, tax, shipping, discount, dates, and status — is mapped onto the Transaction, the ticket is linked back to its original order's Transaction, and the ticket's related data is transferred through child collections: non-gift-card line items, billing and shipping addresses, and payments (one collection per payment type). New tickets are created automatically when the BigCommerce order webhooks are enabled, or on demand from the iPaaS.com Manual Sync page.
ID Format
Manual Sync ID Format
On the iPaaS.com Manual Sync page, enter the BigCommerce order ID — the numeric identifier BigCommerce assigns to the order the deposit ticket is cloned from. Example: 1234.
External ID Format
After a successful transfer, iPaaS.com records the deposit ticket's identifier as the external ID on a dedicated external-ID record. That external-ID record is the primary match that routes a later transfer of the same ticket to the correct Transaction rather than creating a duplicate. The ticket ID — the original order ID with -D appended — is also written into the Transaction's transaction-number field, which gives the ID visibility on the Transaction and serves as a fallback match key when no external-ID record yet exists.
Remapping the transaction-number field to a different source is supported, but it disables that fallback auto-link for any Transactions that existed before the change.
Deleted Record Support
Outbound delete of a deposit ticket is not supported. This family creates and updates Transactions only; no ticket-delete mapping collection ships in the default template, and archiving or removing an order in BigCommerce does not delete the linked ticket Transaction in iPaaS.com. Deposit tickets are intended for downstream accounting use — if your destination system does not use tickets, remove this collection and its children rather than expecting a delete to propagate.
Custom Field Support
BigCommerce custom fields are supported on the Order and Order Product modules. To use a BigCommerce custom field in a mapping, first add it as a custom field in the BigCommerce subscription (Subscription Management → Subscriptions → BigCommerce → Custom Fields), then map it to the corresponding iPaaS.com field on the relevant collection. For Order Product custom fields — including product modifiers that arrive on line items — the custom-field module is BC Order Product, and the custom-field name must match the modifier's display name in BigCommerce. Products must be created with the modifiers for line-item modifier capture to work; see the BigCommerce Products article for how modifiers are configured.
Two iPaaS.com custom fields on the Transaction Line are used by this family out of the box:
Module | Custom Field |
Transaction Line | Original SKU |
Transaction Line | SellingUnit |
Mapping Collection Status
Status: Enabled. The parent deposit-ticket collection is enabled by default. Its filter accepts only order clones whose ID ends in -D that qualify for deposit-ticket handling, and rejects standard orders, gift-card tickets, refunds, and quotes. Review the filter against your business rules before enabling automatic transfers, and remove the whole family if your destination system does not use tickets.
Trigger Events: Automatic transfers run when BigCommerce sends an order webhook to iPaaS.com. Enable the BigCommerce order events (order created and order updated) under the Inbound Data Flows section of the subscription configuration. The external webhooks are
store/order/createdandstore/order/updated. Until these are enabled, no automatic transfers occur; Manual Sync is available at any time.
Duplicate or Conflicting Mappings
Several collections operate on the same BigCommerce order data. Review their filters and Add/Update settings before enabling, and decide which collection is the source of truth for each order state:
Add BigCommerce Deposit Ticket TO iPaaS.com: creates the Transaction for a -D deposit-ticket clone (this family).
Add BigCommerce Order TO iPaaS.com and Update BigCommerce Order TO iPaaS.com: handle standard orders, which are explicitly excluded from deposit-ticket processing.
Add/Update BigCommerce Gift Card Ticket TO iPaaS.com: handles the -GC gift-card-ticket clones.
Add/Update BigCommerce Refund TO iPaaS.com: handles refunds.
The deposit-ticket collection and the standard order collections move different order representations in the same direction (BigCommerce → iPaaS.com). Their filters are coordinated so a given order state is handled by exactly one of them — the order collections reject -D clones, and the deposit-ticket collection requires them.
Important: Enabling overlapping collections without coordinated filters can create duplicate or conflicting Transactions. Confirm each collection's filter selects a distinct set of orders.
Collision Handling
This deposit-ticket family does not use iPaaS.com collision handling — records are routed by external-ID presence (with a fallback match on the existing Transaction's number), not by a collision-recovery step. See ID Format for how the external-ID link and transaction-number fallback prevent duplicates.
Supported Child Collections
Each child below is linked to the parent ticket Transaction and transferred as part of the deposit ticket. The Add parent (Add BigCommerce Deposit Ticket TO iPaaS.com) drives the full set on ticket creation; the line, address, and PayPal children also carry Update variants that refresh their records on later transfers.
Add/Update BigCommerce Deposit Ticket Line TO iPaaS.com: the ticket's non-gift-card line items.
Add/Update BigCommerce Deposit Ticket Billing Address TO iPaaS.com: the ticket billing address.
Add/Update BigCommerce Deposit Ticket Shipping Address TO iPaaS.com: the ticket shipping address.
Add BigCommerce Deposit Ticket CC Payment TO iPaaS.com (credit card / Apple Pay), Add/Update BigCommerce Deposit Ticket Paypal TO iPaaS.com (PayPal), Add BigCommerce Deposit Ticket Gift Card Payment TO iPaaS.com (gift card), Add BigCommerce Deposit Ticket Check Payment TO iPaaS.com (check), and Add BigCommerce Deposit Ticket Test Payment Gateway TO iPaaS.com (test gateway) — the ticket's payments, one collection per payment type.
Unlike the standard order family, the deposit-ticket family does not include separate tax, note, or order-level discount child collections — tax and discounts are carried on the ticket header, and the ticket does not capture customer or staff notes.
System Caveats
BigCommerce Caveats
Deposit tickets are order clones. Only order clones whose ID ends in -D are processed here. The ticket represents the non-gift-card sales portion of the order; gift-card sales are carried on a separate gift-card ticket.
Ticket clones are separate from standard orders. Orders whose ID ends in -D (deposit tickets) or -GC (gift-card tickets) are handled by their own collections, not by the standard order collections.
Different payment types need different mappings. The data BigCommerce returns differs by payment type, so ticket payments are split across gateway-specific child collections (credit card, gift card, check, PayPal, and test gateway). If a ticket uses a payment type not covered by the supplied payment collections, an additional payment sub-collection may be needed — review with your implementation team before relying on it in production.
Rate limiting. When BigCommerce rate-limits requests, the transfer is automatically rescheduled to resume after the limit window resets — no subscriber action is required.
iPaaS.com Caveats
Buyer link. The order's customer or company is transferred as a prerequisite; if that record cannot be created or linked in iPaaS.com, the deposit ticket transfer does not complete.
Original-order link. The ticket links to the original order's Transaction. If that Transaction does not yet exist in iPaaS.com, the ticket is created without a resolved parent link.
Status translation. The ticket status is applied through a lookup translation. Review and customize the translation values so BigCommerce order statuses map to the iPaaS.com Transaction statuses your workflow expects.
Gift-card sales excluded from ticket financials. Gift-card sales are removed from the ticket's subtotal, total, and item quantity — they are carried on a separate gift-card ticket. Ticket payment amounts likewise deduct any gift-card redemption. Expect ticket totals to differ from the raw BigCommerce order totals when the order includes gift cards.
Full-replace updates. Transfers write the full record; fields left unmapped can be overwritten on each transfer. Map every field you want preserved, or use a destination-value approach for fields you do not source from BigCommerce. This behavior is accurate at the time this documentation was written.
Integration-Specific Caveats
Buyer prerequisite. For standard orders the customer is resolved and transferred before the ticket; for B2B orders the company is used instead. Guest orders (no customer) are handled without a buyer prerequisite. A failed buyer prerequisite blocks the ticket transfer.
Payment-method prerequisite. When an order's payment gateway does not yet exist in iPaaS.com, it is created automatically during order preprocessing.
Setup Requirements
Before automatic transfers will run, configure the BigCommerce order webhooks (store/order/created, store/order/updated) and enable the corresponding order events under Inbound Data Flows in the subscription configuration. The store-level API account access token and store hash used for the connection are configured in the subscription settings. For the full webhook and credential walkthrough, see the BigCommerce Installation Instructions and the BigCommerce Connections and Settings article; this document does not duplicate those steps.
Integration Flow
When a deposit ticket is transferred, the integration retrieves the full BigCommerce order and its related records, then dispatches the header and each child to iPaaS.com in order:
The -D order clone is read and evaluated against the collection filter. Clones that do not qualify for deposit-ticket handling, and any order whose ID does not end in -D, are skipped.
Where needed, the buyer is resolved and transferred first: the customer for standard orders, or the company for B2B orders. Guest orders are handled without a buyer prerequisite. Any payment gateway the ticket requires is also created during preprocessing.
The header fields are mapped to the iPaaS.com Transaction. The transaction number is set from the deposit ticket ID (the original order ID with -D appended), and the ticket is linked back to the original order's Transaction so the two records stay associated.
Child records are transferred and linked to the ticket Transaction — non-gift-card line items, billing and shipping addresses, and payments.
On a successful first transfer, iPaaS.com saves the deposit ticket's identifier as the external-ID link so later transfers of the same ticket route to the correct Transaction.
Mappings
Each mapping collection is documented below with its live Mapping Filter, the iPaaS.com data type it targets, and its field-mapping table. In the tables, Dynamic Formula source values are shown inline in backticks; Static values are quoted. The Description column carries the required/recommended classification and behavior for each field.
Add BigCommerce Deposit Ticket TO iPaaS.com
iPaaS.com data type: Transaction
Mapping Filter
( PaymentMethod == "Test Payment Gateway" || RequiresDepositTicket(Transactions_Data, Products_Data)) && Id.EndsWith("-D")Filter Description. The collection processes an order only when both of these are true: the order qualifies for deposit-ticket handling — either its PaymentMethod is Test Payment Gateway, or RequiresDepositTicket(...) determines from the order's transactions and products that a deposit ticket is needed — and the order Id ends in -D, the suffix that identifies a deposit-ticket clone. Standard orders, gift-card tickets (-GC), refunds, and quotes do not meet both conditions and are handled by their own collections. Orders that fail either condition are skipped. No value in this filter is environment-specific, so no placeholder substitution is required.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Dynamic Formula |
| SystemId | Required. Sets the source system for the Transaction to the BigCommerce system this subscription is connected to — the Transaction must record which system the deposit ticket came from. |
Dynamic Formula |
| TransactionNumber | Required. Stores the deposit ticket ID on the Transaction — the original BigCommerce order ID with -D appended. It gives the ID visibility on the Transaction and acts as a fallback match key before an external-ID link exists. |
Dynamic Formula |
| ParentId | Recommended. Links the deposit ticket back to its original order's Transaction. The formula strips the trailing -D from the ticket ID to recover the original order ID, then resolves that order's iPaaS.com Transaction. If the original order has not yet been transferred, this link cannot be resolved. |
Static |
| Type | Required. Fixed value — sets the Transaction type to Ticket. Every record in this collection is a deposit ticket. |
Dynamic Formula | Dynamic Formula (customer resolution) | CustomerId | Recommended. Links the Transaction to the buyer's iPaaS.com Customer for standard (non-B2B) orders. For B2B orders this is left unset and the company is used instead. The buyer is transferred as a prerequisite. One of |
Dynamic Formula | Dynamic Formula (company resolution) | CompanyId | Recommended for B2B orders. Links the Transaction to the buyer's iPaaS.com Company for B2B orders; left unset for standard orders (which use |
Dynamic Formula | Dynamic Formula (email resolution) | EmailAddress | Recommended. Sets the ticket email — the company email for B2B orders, otherwise the billing-address email, falling back to a guest email when the order has no customer. See the placeholder note below the table. |
Lookup Translation | Lookup Translation: BigCommerce Order Status → Transaction Status | Status | Recommended. Translates the BigCommerce order status into the iPaaS.com Transaction status. Review and customize the translation values so each BigCommerce status maps to the Transaction status your workflow expects. |
Dynamic Formula | Dynamic Formula (order discount + coupons, excluding shipping coupons) | DiscountAmount | Recommended. Calculates the ticket's total discount: the order discount amount plus every coupon discount, excluding shipping-type coupons (which are not counted as order discounts). |
Field | order TotalTax | TaxAmount | Recommended. Maps the order's total tax to the ticket Transaction. |
Field | order ShippingCostExTax | ShippingAmount | Recommended. Maps the order's shipping cost (excluding tax) to the ticket Transaction. |
Dynamic Formula |
| Subtotal | Recommended. Calculates the ticket subtotal from the total value of products sold. Gift-card sales are excluded — they are carried on a separate gift-card ticket — so only non-gift-card product value contributes. |
Dynamic Formula | Dynamic Formula (rebuilt ticket total) | Total | Recommended. Recalculates the ticket grand total. Because gift-card sales are removed from the subtotal, the total is rebuilt from the product-sold total plus tax and shipping, less order and coupon discounts, then adds shipping-type coupon discounts back in (they were already deducted from the shipping amount). |
Dynamic Formula |
| TotalQty | Recommended. Sets the total item quantity on the ticket from the count of products sold, excluding gift-card items. |
Field | order DateCreated | TransactionCreatedDateTime | Recommended. Preserves the original BigCommerce order creation date/time on the ticket Transaction. |
Field | order DateModified | TransactionUpdatedDateTime | Recommended. Preserves the BigCommerce order last-modified date/time on the ticket Transaction. |
Placeholder value — replace during implementation: the guest fallback email Guest@theredrookqa.com used by the EmailAddress formula is an example test-domain address. Replace it with the email your business wants to record on guest orders before enabling this collection.
The buyer-resolution, company-resolution, email-resolution, discount, and total formulas are configurable dynamic formulas maintained on the mapping. Their behavior is summarized in the Description column above; the full expression bodies are recoverable from a live iPaaS.com subscription export.
Lookup Translation Tables
The Status field above uses the BigCommerce Order Status → Transaction Status lookup translation. These are subscriber-configurable defaults; review and customize them so each BigCommerce status maps to the Transaction status your workflow expects.
Source Value (BigCommerce) | Destination Value (iPaaS.com) |
Cancelled | Cancelled |
Completed | Complete |
Awaiting Payment | Pending |
Awaiting Shipment | Pending |
Partially Shipped | Pending |
Awaiting Fulfillment | Pending |
Awaiting Pickup | Pending |
Shipped | Shipped |
Refunded | Refunded |
Partially Refunded | Partially Refunded |
Add/Update BigCommerce Deposit Ticket Line TO iPaaS.com
iPaaS.com data type: Transaction Line
Mapping Filter
Type != "giftcertificate"
Filter Description. The collection processes an order line only when its Type is not giftcertificate — gift-certificate lines are excluded because the deposit ticket represents the non-gift-card sales portion of the order (gift-card sales are carried on a separate gift-card ticket). Every non-gift-certificate line passes through.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Dynamic Formula |
| SellingUnit | Recommended. Derives the selling unit for the line by parsing the line's SKU — it identifies the unit of measure when a product is sold in an alternate unit. |
Lookup Translation | Lookup Translation: BigCommerce Line Type → Transaction Line Type | Type | Recommended. Translates the BigCommerce line type into the iPaaS.com Transaction Line type. Review and customize the translation values so each line type maps as your workflow expects. |
Static |
| Status | Recommended. Fixed value — sets the line status to Pending for every line. This is a genuine status constant, not an environment-specific value. |
Dynamic Formula |
| Sku | Recommended. Derives the product SKU for the line by parsing the line's SKU, recovering the base SKU when the product is sold in an alternate unit — it identifies the product on the line. |
Field | order line Name | Description | Recommended. Maps the item name to the line description. |
Field | order line Quantity | Qty | Recommended. Maps the ordered quantity to the line. |
Field | order line QuantityShipped | QtyShipped | Recommended. Maps the shipped quantity to the line. |
Dynamic Formula |
| UnitPrice | Recommended. Calculates the per-item price after discounts (BigCommerce does not provide a unit price directly): the post-discount line total divided by the quantity, or 0 when the quantity is zero. |
Dynamic Formula |
| ExtendedPrice | Recommended. Calculates the after-discount extended price (BigCommerce does not expose it directly): the pre-tax line total minus the sum of applied discounts. |
Field | order line BasePrice | OriginalUnitPrice | Recommended. Maps the line's base (pre-discount) unit price to the line. |
Dynamic Formula |
| DiscountAmount | Recommended. Sums every discount applied to this line and records the total as the line discount amount. |
Field | order line TotalTax | EstimatedTaxAmount | Recommended. Maps the line's total tax to the estimated tax amount. |
Field | order line Weight | Weight | Recommended. Maps the item weight to the line. |
Lookup Translation Tables
The Type field above uses the BigCommerce Line Type → Transaction Line Type lookup translation. These are subscriber-configurable defaults; review and customize them so each line type maps as your workflow expects.
Source Value (BigCommerce) | Destination Value (iPaaS.com) |
digital | Product |
giftcertificate | Gift Card |
physical | Product |
Add/Update BigCommerce Deposit Ticket Billing Address TO iPaaS.com
iPaaS.com data type: Transaction Address
Mapping Filter
SourceTypeName == "ParentOnly"
Filter Description. The collection processes the address only when SourceTypeName is ParentOnly — that is, once per ticket, from the order header's billing address rather than from a per-line or per-shipment source. This ensures exactly one primary billing address is created for the ticket.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Static |
| IsPrimaryBilling | Recommended. Fixed value — flags this address as the ticket's primary billing address. A genuine constant for this collection, not an environment-specific value. |
Dynamic Formula |
| Address1 | Recommended. Maps the first billing street line from the parent order's billing address. |
Dynamic Formula |
| Address2 | Recommended. Maps the second billing street line from the parent order's billing address. |
Dynamic Formula |
| City | Recommended. Maps the billing city from the parent order's billing address. |
Dynamic Formula |
| Region | Recommended. Maps the billing state or region from the parent order's billing address. |
Dynamic Formula |
| Country | Recommended. Maps the billing country from the parent order's billing address. |
Dynamic Formula |
| PostalCode | Recommended. Maps the billing postal code from the parent order's billing address. |
Dynamic Formula |
| FirstName | Recommended. Maps the billing contact's first name from the parent order's billing address. |
Dynamic Formula |
| LastName | Recommended. Maps the billing contact's last name from the parent order's billing address. |
Dynamic Formula |
| Company | Recommended. Maps the billing company name from the parent order's billing address. |
Add/Update BigCommerce Deposit Ticket Shipping Address TO iPaaS.com
iPaaS.com data type: Transaction Address
Mapping Filter
SourceTypeName == "OrderShippingAddress"
Filter Description. The collection processes the address only when SourceTypeName is OrderShippingAddress — the order's shipping-address source. This keeps the shipping address distinct from the billing address (which is created by the billing-address collection) so each ticket gets one primary shipping address.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Static |
| IsPrimaryShipping | Recommended. Fixed value — flags this address as the ticket's primary shipping address. A genuine constant for this collection, not an environment-specific value. |
Field | shipping address Street1 | Address1 | Recommended. Maps the first shipping street line. |
Field | shipping address Street2 | Address2 | Recommended. Maps the second shipping street line. |
Field | shipping address City | City | Recommended. Maps the shipping city. |
Field | shipping address State | Region | Recommended. Maps the shipping state or region. |
Field | shipping address Country | Country | Recommended. Maps the shipping country. |
Field | shipping address Zip | PostalCode | Recommended. Maps the shipping postal code. |
Lookup Translation | Lookup Translation: BigCommerce Shipping Method → iPaaS.com Shipping Method | ShippingMethod | Recommended. Translates the BigCommerce shipping method into the iPaaS.com shipping method. Review and customize the translation values so each BigCommerce shipping method maps as your workflow expects. |
Field | shipping address ShippingMethod | ShippingMethodDescription | Recommended. Records the original BigCommerce shipping-method label as the description, preserving the raw value alongside the translated |
Field | shipping address FirstName | FirstName | Recommended. Maps the recipient's first name. |
Field | shipping address LastName | LastName | Recommended. Maps the recipient's last name. |
Field | shipping address Company | Company | Recommended. Maps the recipient company name. |
Lookup Translation Tables
The ShippingMethod field above uses the BigCommerce Shipping Method → iPaaS.com Shipping Method lookup translation.
Placeholder value — replace during implementation: the pairs below are example UPS mappings from the development store. Replace them with your store's actual shipping-method names and the values your destination system expects before go-live.
Source Value (BigCommerce) | Destination Value (iPaaS.com) |
UPS (UPS Ground) | UPS GROUND |
None | UPS GROUND |
UPS (UPS 3 Day Select) | UPS GROUND |
UPS (UPS 2nd Day Air) | UPS BLUE |
UPS (UPS Next Day Air) | UPS RED |
Flat Rate | UPS GROUND |
Add BigCommerce Deposit Ticket CC Payment TO iPaaS.com
iPaaS.com data type: Transaction Payment
This collection covers credit card and Apple Pay payments (and captures for those) on the deposit ticket.
Mapping Filter
!(Parent.PaymentMethod == "PayPal") && !(Parent.PaymentMethod == "Test Payment Gateway") && !(Parent.PaymentMethod == "Test Payment Provider") && (Event == "capture" || (Event == "authorization" && CreditCardAuthIsCaptured(GatewayTransactionId, Parent.Transactions_Data) == false) || (Event == "purchase" && Method == "credit_card") && Status == "ok" )
Filter Description. The collection processes a payment only when the order's payment method is not PayPal, Test Payment Gateway, or Test Payment Provider (those are handled by their own collections), and the payment event qualifies as one of: a capture event; an authorization event that has not already been captured (CreditCardAuthIsCaptured(...) == false); or a purchase event whose Method is credit_card with Status ok. Payments that do not meet one of these event conditions are skipped so an authorization already represented by a later capture is not double-counted. No value in this filter is environment-specific.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Dynamic Formula |
| Method | Recommended. Resolves the payment method, examining the order's payment data and related transactions. Outputs a specific credit-card brand (Visa, Discover, MasterCard, or American Express), a generic credit card when the brand cannot be determined, Apple Pay, PayPal, gift card, or Other. Apple Pay is recognized only when BigCommerce labels the method with the exact standard Apple Pay value (and Apple Pay carries no card brand); a relabeled method may resolve differently. |
Dynamic Formula |
| Description | Optional. Passes the resolved payment method through as the payment description, preserving any detail beyond the standard method mapping. |
Dynamic Formula | Dynamic Formula (product-sold total less gift-card redemption) | Amount | Recommended. Calculates the ticket payment amount: the product-sold total plus tax and shipping, less any gift-card redemption and order and coupon discounts, with shipping-type coupon discounts added back in (they were already deducted from the shipping amount). Gift-card redemptions are deducted because gift-card sales are carried on a separate ticket. |
Dynamic Formula |
| Status | Recommended. Sets the payment status to Captured for a capture or purchase event, and Authorized otherwise. |
Add/Update BigCommerce Deposit Ticket Paypal TO iPaaS.com
iPaaS.com data type: Transaction Payment
This collection covers PayPal payments on the deposit ticket.
Mapping Filter
SourceTypeName == "ParentOnly" && Parent.PaymentMethod.StartsWith("PayPal")Filter Description. The collection processes the payment only when SourceTypeName is ParentOnly (once per ticket, from the order header) and the order's PaymentMethod starts with PayPal. Non-PayPal orders, and per-line payment sources, are skipped. No value here is environment-specific.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Dynamic Formula |
| Method | Recommended. Runs the standard payment-method resolution, which for this collection returns PayPal because the filter restricts it to PayPal orders. |
Dynamic Formula |
| Description | Optional. Passes the order's BigCommerce payment method name through as the payment description. |
Dynamic Formula | Dynamic Formula (product-sold total less gift-card redemption) | Amount | Recommended. Calculates the ticket payment amount: the product-sold total plus tax and shipping, less any gift-card redemption and order and coupon discounts, with shipping-type coupon discounts added back in. Gift-card redemptions are deducted because gift-card sales are carried on a separate ticket. |
Dynamic Formula |
| Status | Recommended. Sets the status to Captured when the order's PayPal payment status is captured, and Authorized otherwise. |
Add BigCommerce Deposit Ticket Gift Card Payment TO iPaaS.com
iPaaS.com data type: Transaction Payment
This collection covers gift-card (gift-certificate) payments applied to the deposit ticket.
Mapping Filter
Method == "gift_certificate"
Filter Description. The collection processes a payment only when its Method is gift_certificate. All other payment methods are skipped and handled by the credit card, PayPal, check, or test-gateway collections.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Dynamic Formula | Dynamic Formula (gift-card number → method-info data) | MethodInfo | Recommended. Records the gift-card number used for this payment. Because the number cannot be mapped directly to a field, the integration reads the gift-card number for the gift certificate and stores it in the payment's method-info data — it identifies which gift card was applied to the ticket. |
Dynamic Formula |
| Method | Recommended. Resolves the payment method; for a gift-certificate payment it returns the gift-card method value. |
Dynamic Formula |
| Description | Optional. Passes the resolved method value through as the payment description, preserving any detail beyond the standard payment mapping. |
Field | payment Amount | Amount | Recommended. Maps the gift-card payment amount to the ticket payment. |
Field | payment Status | Status | Recommended. Maps the BigCommerce payment status to the ticket payment. |
Add BigCommerce Deposit Ticket Check Payment TO iPaaS.com
iPaaS.com data type: Transaction Payment
This collection covers online (website) check payments on the deposit ticket.
Mapping Filter
!(Parent.PaymentMethod == "PayPal") && !(Parent.PaymentMethod == "Test Payment Gateway") && !(Parent.PaymentMethod == "Test Payment Provider") && (Event == "capture" || (Event == "authorization" && CreditCardAuthIsCaptured(GatewayTransactionId, Parent.Transactions_Data) == false) || (Event == "purchase" && Method == "credit_card") && Status == "ok" )
Filter Description. The collection processes a payment only when the order's payment method is not PayPal, Test Payment Gateway, or Test Payment Provider, and the payment event qualifies as a capture, an uncaptured authorization (CreditCardAuthIsCaptured(...) == false), or a purchase whose Method is credit_card with Status ok. Payments that do not meet one of these event conditions are skipped. No value here is environment-specific.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Dynamic Formula | Dynamic Formula (match existing Check payment method, else Check) | Method | Recommended. Looks up a configured check payment-method name in iPaaS.com and uses it when found; otherwise records the method as Check. To have this payment recorded under a specific payment-method name, configure that name in your iPaaS.com payment methods. |
Static |
| Description | Optional. Sets the payment description to Website Check, a readable label identifying the payment as an online check. Subscribers may customize this label to match the wording their downstream system expects. |
Dynamic Formula | Dynamic Formula (product-sold total less gift-card redemption) | Amount | Recommended. Calculates the ticket payment amount: the product-sold total plus tax and shipping, less any gift-card redemption and order and coupon discounts, with shipping-type coupon discounts added back in. Gift-card redemptions are deducted because gift-card sales are carried on a separate ticket. |
Static |
| Status | Recommended. Fixed value — sets the payment status to Authorized for every check payment. A genuine status constant for this collection, not an environment-specific value. |
Add BigCommerce Deposit Ticket Test Payment Gateway TO iPaaS.com
iPaaS.com data type: Transaction Payment
This collection covers test-gateway payments on the deposit ticket.
Mapping Filter
SourceTypeName == "ParentOnly" && (Parent.PaymentMethod == "Test Payment Gateway" || Parent.PaymentMethod == "Test Payment Provider")
Filter Description. The collection processes the payment only when SourceTypeName is ParentOnly (once per ticket, from the order header) and the order's PaymentMethod is either Test Payment Gateway or Test Payment Provider. All other payments are skipped. No value here is environment-specific.
Mapping Type | Source Field (BigCommerce) | Destination Field (iPaaS.com) | Description |
Static |
| Method | Recommended. Fixed value — sets the payment method to Other for every test-gateway payment. The Test Payment Gateway and Test Payment Provider carry no real payment-instrument type, so the standard payment-method resolution does not apply here; Other is the genuine method value for this collection, not an environment-specific placeholder. |
Dynamic Formula |
| Description | Optional. Passes the order's BigCommerce payment method name through as the payment description. |
Dynamic Formula | Dynamic Formula (product-sold total less gift-card redemption) | Amount | Recommended. Calculates the ticket payment amount: the product-sold total plus tax and shipping, less any gift-card redemption and order and coupon discounts, with shipping-type coupon discounts added back in. Gift-card redemptions are deducted because gift-card sales are carried on a separate ticket. |
Static |
| Status | Recommended. Fixed value — sets the payment status to Captured for every test-gateway payment. A genuine status constant for this collection, not an environment-specific value. |
Error Handling
The BigCommerce integration reports errors through the standard iPaaS.com error path. For the catalog of transaction-related error messages and how to resolve them, see the BigCommerce Integration - Error Messages article rather than duplicating it here. Two behaviors specific to this family are worth noting:
Rate limiting. When BigCommerce rate-limits requests, the transfer is automatically rescheduled to resume after the limit window resets — no subscriber action is required.
Buyer prerequisite failure. If the order's customer or company cannot be created or linked in iPaaS.com, the deposit ticket transfer does not complete. Confirm the buyer record can be resolved before re-running the transfer.
Testing & Validation
Test Scenarios
Create a new deposit ticket. Place a completed BigCommerce order that qualifies for deposit-ticket handling (for example, an order paid with the Test Payment Gateway, with at least one non-gift-card line item, a billing and shipping address, and a payment) and verify the -D clone transfers to iPaaS.com as a Ticket-type Transaction with the correct transaction number, buyer, totals, lines, addresses, and payment.
Original-order link. Confirm the ticket Transaction is linked back to the original order's Transaction — transfer the original order first, then the ticket, and verify the parent link resolves.
Filter rejection. Confirm that a standard order (no -D suffix), a -GC gift-card ticket, a refund, and a quote-originated order are each skipped by the deposit-ticket collection.
ID format. From the Manual Sync page, transfer a ticket by its numeric BigCommerce order ID and confirm the transfer succeeds and the external-ID link is saved.
Payment-type coverage. Place qualifying orders paid by credit card, Apple Pay, PayPal, gift card, check, and the test gateway, and verify each is captured by the matching payment collection with the expected method, amount, and status.
Gift-card exclusion. Place a qualifying order that includes a gift-card sale and verify the ticket's subtotal, total, item quantity, and payment amount exclude the gift-card value (which is carried on a separate gift-card ticket).
Guest order. Place a qualifying guest order (no customer) and confirm the email falls back correctly — after replacing the placeholder guest email with your own value.
Validation Checklist
The Transaction type is Ticket and its transaction number equals the BigCommerce order ID with -D appended.
The ticket is linked to the original order's Transaction through its parent link.
The buyer is linked as a Customer (standard order) or Company (B2B order).
Ticket financials — Total, Subtotal, TaxAmount, ShippingAmount, DiscountAmount, TotalQty — reflect the non-gift-card portion of the order.
Only non-gift-certificate line items appear on the ticket, each with the correct SKU, quantity, unit price (after discount), extended price, tax, and weight.
Billing and shipping addresses are flagged as primary and carry the correct contact and address fields.
The order status maps to the intended Transaction status through the status lookup translation.
The placeholder guest email has been replaced before enabling the collections.
Payment amounts exclude any gift-card redemption.
Additional Notes
Tickets are intended for accounting systems. Deposit tickets are designed to be sent along to an ERP for use in accounting systems. If your destination system does not use tickets, this collection and its children can be removed.
Standard orders are handled by the standard Order collections, not the deposit-ticket collections.
Gift-card tickets (the -GC order clones) are handled by their own collections, and gift-card sales are carried there rather than on the deposit ticket.
Refunds are handled by the Refund collections.
Full details of the read and write endpoints this integration uses are in the BigCommerce API Endpoints article.
For the full list of integration-wide constraints, see the BigCommerce Integration Known Limitations article.