This article describes the known limitations of the 99minds integration for iPaaS.com. These limitations are inherent to the current design of the integration and the capabilities of the 99minds API, and they apply to all subscribers at the time this documentation was written. As the 99minds platform and API evolve, some of these limitations may change.

The integration does not perform a bulk import of existing 99minds data when the subscription is first connected. There is no "initialize" step that backfills historical customers, loyalty transactions, or gift cards.

What this means for you: All mapping collections must be configured manually, and records sync going forward as they are created or changed. To bring existing data across, transfer the relevant records individually using Manual Sync.

The integration creates and updates records only. Deleting a record in one system does not delete the linked record in the other — there is no delete operation in any of the mapping collections.

What this means for you: If you remove a customer, loyalty transaction, or gift card in one system, you must remove it in the other system yourself if you want the two to stay aligned. Lifecycle changes such as deactivating, blocking, or voiding a gift card are reflected as status updates rather than deletions.

Transfers from 99minds into iPaaS.com (customer and loyalty point events) are driven by 99minds webhooks. The integration does not subscribe to these events automatically — each webhook must be created manually in the 99minds portal using your iPaaS.com subscription Webhook API Key.

What this means for you: No customer or loyalty data flows from 99minds into iPaaS.com until you configure the webhooks in 99minds (Settings > Webhooks > Manage). See the 99minds Installation Instructions for the exact steps. Until the webhook is in place, use Manual Sync to bring individual records into iPaaS.com.

Customers and gift cards can move in both directions (into and out of iPaaS.com). When both directions are enabled for the same record, a change made in one system can overwrite a more recent change made in the other.

What this means for you: Decide which system is the system of record for each data type so the two directions do not overwrite one another. If you need to keep specific fields from being overwritten when a record is updated, map those fields so they retain the existing destination value rather than the incoming value (the customer update collection already preserves identity fields this way).

Note: This applies to the Customer and Gift Card collections, which exist in both the TO iPaaS.com and FROM iPaaS.com directions. The loyalty point and order collections move in a single direction and are not affected.

When a 99minds customer is brought into iPaaS.com, the iPaaS.com Customer Number is taken from the 99minds Phone field. A 99minds customer with no phone value receives "N/A" as its Customer Number.

What this means for you: Because the Customer Number is a unique identifier in iPaaS.com, confirm that your 99minds customers reliably have a Phone value before relying on it for matching. Customers without a phone value will all share the "N/A" Customer Number, which can affect how they are matched.

A gift card cannot be issued in 99minds without a campaign. The campaign is supplied through the Campaign Id subscription setting (or as a mapped field).

What this means for you: Set the Campaign Id to a valid 99minds campaign before transferring gift cards from iPaaS.com. Without it, gift card issuance fails. The campaign is found under Programs in the 99minds portal.

When a gift card is issued with a customer email that does not match an existing 99minds customer, 99minds creates a new customer (without a name) from that email so the card can be linked.

What this means for you: If you do not want gift card transfers to create customers in 99minds, make sure the gift card resolves to a customer that already exists — transfer the customer first, or map the receiving email through the validation option that returns the email only when a matching 99minds customer already exists.

Loyalty point balances are recorded and adjusted through the loyalty card transaction collections. The customer collections do not change loyalty balances, and iPaaS.com does not write loyalty point balances back to 99minds.

What this means for you: Treat 99minds as the system of record for loyalty point balances. iPaaS.com reflects loyalty activity from 99minds on the customer and on transactions, but does not push balance changes back to 99minds.

When loyalty activity arrives from 99minds, Reload and Redemption transaction types are excluded from creating a new loyalty point transaction in iPaaS.com, as are zero-amount adjustments.

What this means for you: Only genuine point earn and redemption events become loyalty transaction records in iPaaS.com. Reload and Redemption events, and adjustments with a zero amount, are intentionally skipped.

When gift cards are sent from iPaaS.com to 99minds, the example mappings link each card to its 99minds customer using the receiving customer's email address. When a receiving email is present it is used to find (or create) the customer, and the linked Customer Id is used only when no receiving email is available.

What this means for you: This is an implementation item to check. If your gift cards do not reliably include a receiving customer email, review and adjust the customer mappings on the Add/Update 99minds Gift Card FROM iPaaS.com collection before relying on it in production — for example, so the card is linked by its Customer Id when no email is present. Validate the behavior in a staging environment first.

Sending a gift card from iPaaS.com only issues a new card or reloads/redeems its balance. The integration has no operation that changes a card's status — it cannot activate, deactivate, or void a card, and there is no delete.

What this means for you: To take a gift card out of use from iPaaS.com, change the values the integration acts on rather than expecting a status change. Setting the iPaaS.com Balance to 0 — or changing the card to a terminal status (Expired, Void, or Redeemed), which forces the transferred amount to 0 — causes the card to be redeemed to a zero balance on the next transfer, so it can no longer be spent. Activating, deactivating, or voiding a card by status in 99minds must still be done in the 99minds portal; iPaaS.com reflects those lifecycle states by zeroing the balance rather than by changing the 99minds status. (Expiration date handling is covered separately below.)

An expiration date sent from iPaaS.com can move a card's expiration later, but never earlier. The expiration is included when a card is first issued, and on a later update the integration sends the new date to 99minds (through its extend expiry operation) only when the date has changed. 99minds rejects any date earlier than the card's current expiration with the error "Expiration date cannot be less than the current one," and the transfer fails.

What this means for you: Use iPaaS.com to set or extend a card's expiration to the same or a later date. To shorten a card's life or take it out of use before its expiration, do not send an earlier date — instead set the card's status to Void or Expired (or set the Balance to 0) so the card is redeemed to a zero balance and can no longer be spent.

99minds VIP tiers sync into iPaaS.com as Customer Categories. Three behaviors are inherent to how 99minds manages tiers:

What this means for you: Treat 99minds as the source of truth for the VIP-tier category only. Tier assignment rides the Customer integration and never creates a customer — if a tier.changed event arrives for a 99minds customer that has no matching iPaaS.com customer (no external-id link and no matching email), the assignment is not applied and no customer is created; the integration raises an exception so the unmatched event is surfaced for follow-up rather than silently dropped.

This document covers thirteen known limitations of the 99minds integration. For detailed, per-collection technical documentation, refer to the 99minds mapping collection descriptions and the mapping documentation articles.

Setup & Reference

Mapping Documentation