Overview
This article catalogs the error messages you may encounter while synchronizing data between iPaaS.com and 99minds, grouped by the mapping collection flow that produces them. Each error carries a stable code (for example, 99MN-VALD-1001) that you can search for on this page (Ctrl+F / Cmd+F) — the code stays the same even if the wording is refined later, so it is the most reliable way to find an error.
When a transfer to 99minds fails, iPaaS.com records the error in the subscription's error logs prefixed with Unable to process transfer. Reason: followed by the message shown below. For example, an invalid campaign produces Unable to process transfer. Reason: 99MN-EXTN-1002 - Gift Card creation failed: Invalid campaign_id.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Supported Flows
Add/Update 99minds Gift Card FROM iPaaS.com
Add/Update 99minds Gift Card TO iPaaS.com
99minds Customer FROM iPaaS.com
99minds Customer TO iPaaS.com
99minds Loyalty Card Transaction TO iPaaS.com
Add 99minds Order Completed Workflow FROM iPaaS.com
Add/Update 99minds Tier TO iPaaS.com
Error Collection
General (all flows)
99minds API call failed
99MN-EXTN-1001 - Error calling 99minds [action]: [response] (Http Code: [status])
Description: 99minds rejected an API call the integration made on your behalf and returned an error response (for example, an HTTP 400 or 404). The message includes the action being attempted and the response 99minds returned. This is the general wrapper for any 99minds API failure that a more specific code below does not cover — including a duplicate Gift Card ("The card is already issued or sold") when the collection's Collision Handling Method is set to Error (see Duplicate card already issued under the Gift Card FROM flow).
Resolution: Read the response 99minds returned in the error — it names the exact problem (an invalid field value, a missing record, or an authentication issue). Correct the source data or the mapping that produced the value, then retry the transfer. If the response indicates a credentials or permissions problem, confirm the API Key on the Subscription Settings page is valid for the 99minds account. If the message points to a configuration your Managed Integration Service Provider (MiSP) manages — mappings, presets, or collision settings — your MiSP can adjust it.
Unexpected empty response on lookup
99MN-INTL-1002 - An unexpected error occurred while processing the request.
Description: The integration requested a Customer or Gift Card record from 99minds during a transfer TO iPaaS.com, and 99minds returned a success response with no record data. This can happen if the record was removed in 99minds between the time it was queued and the time it was retrieved.
Resolution: Confirm the record still exists in 99minds. If it was deleted or is no longer accessible in the 99minds account being synced, the transfer cannot complete and can be disregarded. If the record does exist and the error repeats, this indicates an unexpected response from 99minds — your MiSP or iPaaS.com Support can investigate the returned data using the error timestamp and the affected record ID.
Add/Update 99minds Gift Card FROM iPaaS.com
Amount not greater than zero
99MN-VALD-1001 - Gift Card creation failed: Amount must be greater than zero.
Description: A Gift Card cannot be issued with a zero or negative amount. The amount comes from the iPaaS.com Gift Card Balance.
Resolution: Confirm the iPaaS.com Gift Card has a Balance greater than 0 before transferring. Active gift cards with a remaining balance are the only records the collection processes.
Campaign Id missing
99MN-VALD-1002 - Gift Card creation failed: CampaignId is required. Provide it via field mapping or the 'Campaign Id' preset.
Description: 99minds requires a campaign to issue a Gift Card, and none was supplied.
Resolution: Set the Campaign Id subscription preset to a valid 99minds campaign (found under Programs in the 99minds portal), or map the campaign as a field on the collection.
No customer identifier
99MN-VALD-1003 - Gift Card creation failed: At least one customer identifier is required (CustomerEmail, CustomerId, or ClientCustomerId with ClientCustomerPlatform).
Description: A Gift Card must be linked to a customer, but no usable customer identifier was resolved from the iPaaS.com record.
Resolution: Make sure the Gift Card resolves a customer — map ReceivingCustomerEmail, or confirm the record's CustomerId links to a 99minds customer. Transfer the customer to 99minds first if it has not been synced.
Card reference missing on update
99MN-VALD-1004 - Gift Card update failed: Either CardId or GiftCardNumber is required.
Description: Updating a Gift Card requires either the linked 99minds card id or a card number to locate the card, and neither was available.
Resolution: Confirm the Gift Card was previously issued and linked, or that a Customer Card Number is mapped so the card can be located in 99minds.
Negative update amount
99MN-VALD-1005 - Gift Card update failed: Amount must be zero or greater.
Description: A Gift Card balance cannot be reconciled to a negative value.
Resolution: Confirm the iPaaS.com Gift Card Balance is zero or greater before transferring.
Card not found by number
99MN-NFND-1001 - Gift Card update failed: Could not resolve CardId for GiftCardNumber '{GiftCardNumber}'.
Description: The integration looked up the Gift Card by its number in 99minds but found no match.
Resolution: Confirm the card number exists in 99minds and is spelled exactly as stored. If the card was issued through a different system, verify it is present in the 99minds account being synced.
Current card state unavailable
99MN-NFND-1002 - Gift Card update failed: Could not retrieve current card state for card_id '{CardId}'.
Description: The integration could not load the existing 99minds card before reloading or redeeming — for example, the linked card id no longer resolves in 99minds.
Resolution: Confirm the card still exists in 99minds. If it was deleted or voided in 99minds, the iPaaS.com record can no longer be reconciled to it.
Gift Card creation rejected by 99minds
99MN-EXTN-1002 - Gift Card creation failed: [message returned by 99minds]
Description: 99minds rejected the Gift Card issuance and returned a reason. A common example is Invalid campaign_id, which means the supplied Campaign Id does not match a campaign in 99minds.
Resolution: For Invalid campaign_id, verify the Campaign Id matches a valid campaign under Programs in 99minds. For other messages, review the reason 99minds returned and correct the card or customer value it names, then retry.
Gift Card reload rejected by 99minds
99MN-EXTN-1003 - Gift Card reload failed: [message returned by 99minds]
Description: 99minds rejected the reload (balance increase) and returned a reason.
Resolution: Review the reason 99minds returned, confirm the card is active and eligible for reload, correct the value it names, and retry.
Gift Card redeem rejected by 99minds
99MN-EXTN-1004 - Gift Card redeem failed: [message returned by 99minds]
Description: 99minds rejected the redeem (balance decrease) and returned a reason.
Resolution: Review the reason 99minds returned, confirm the card is active and has sufficient balance to redeem, and retry.
Gift Card expiry extension rejected by 99minds
99MN-EXTN-1005 - Gift Card extend expiry failed: [message returned by 99minds]
Description: The iPaaS.com Gift Card's Expiration Date changed, and 99minds rejected the request to extend the card's expiry, returning a reason.
Resolution: Review the reason 99minds returned and confirm the card is active and the new Expiration Date is valid for the card's campaign, then retry.
Prerequisite customer could not be created for Gift Card
99MN-EXTN-1009 - Unable to create the customer required for this Gift Card. This prevented the gift card from being issued.
Description: Before a Gift Card can be issued, its recipient customer must exist in 99minds. The integration attempted to create that customer first and the customer transfer failed, so the Gift Card was not issued.
Resolution: Look for the customer transfer's own error in the same activity log (it will carry its own code, such as
99MN-EXTN-1006) and resolve that first — most often a missing or invalid recipient email. Once the customer transfers successfully, retry the Gift Card. If the customer mapping needs adjustment, contact your MiSP.
Duplicate card already issued
The card is already issued or sold (surfaces as 99MN-EXTN-1001 when Collision Handling is set to Error)
Description: 99minds rejected the issuance because a Gift Card with the same card number already exists. When collision handling is enabled, the integration recovers automatically — it finds the existing card by its number and completes the transfer as an update instead of creating a duplicate. When the Collision Handling Method is set to Error, the duplicate is not recovered and the 99minds message surfaces under code
99MN-EXTN-1001.Resolution: No action is needed when collision handling is configured and the Customer Card Number is set and unique. To control how duplicates are handled, set the Collision Handling Method on the mapping collection to your preferred behavior (Error, Remap and Link, Update and Link, or Update and No Link). If recovery does not occur, confirm the Customer Card Number is mapped and unique.
Balance could not be read
99MN-INTL-1001 - Gift Card update failed: Unable to parse current balance '{Balance}'.
Description: 99minds returned a card balance the integration could not interpret as a number.
Resolution: Confirm the card's balance in the 99minds portal looks correct. If it does and the error repeats, this is an unexpected value returned by 99minds — your MiSP or iPaaS.com Support can investigate it using the error timestamp and the affected card id.
Add/Update 99minds Gift Card TO iPaaS.com
Prerequisite customer could not be created for Gift Card
99MN-EXTN-1013 - Unable to create the customer required for this Gift Card. This prevented the gift card from transferring to iPaaS.com.
Description: Before a Gift Card can transfer into iPaaS.com, its associated customer must exist in iPaaS.com. The integration attempted to transfer that customer first and it failed, so the Gift Card did not transfer.
Resolution: Look for the customer transfer's own error in the same activity log and resolve it first, then retry the Gift Card. If the customer mapping or link needs adjustment, contact your MiSP.
Prerequisite customer could not be transferred by email for Gift Card
99MN-EXTN-1014 - Unable to transfer the customer (by email) required for this Gift Card. This prevented the gift card from transferring to iPaaS.com.
Description: The Gift Card had no direct customer id, so the integration matched the customer by email and attempted to transfer that customer into iPaaS.com first. That customer transfer failed, so the Gift Card did not transfer.
Resolution: Confirm the customer's email in 99minds resolves to a single valid customer, then resolve the customer transfer's own error in the log and retry. If the matching or mapping needs adjustment, contact your MiSP.
Existing gift card could not be linked by number
99MN-BIZL-1005 - Unable to dynamically link to an existing iPaaS.com Gift Card using Gift Card Number {GiftCardNumber}. This may result in duplicate gift card records.
Description: iPaaS.com already had a Gift Card with this number, and the integration attempted to link the two records so the transfer would update the existing card rather than create a new one. The link could not be confirmed, so a duplicate may be created.
Resolution: Check whether a Gift Card with this number already exists in iPaaS.com. If a duplicate was created, your MiSP can reconcile the external-ID link between the 99minds card and the iPaaS.com record so future transfers update the correct card.
99minds Customer FROM iPaaS.com
Customer creation rejected by 99minds
99MN-EXTN-1006 - Customer creation failed for [email]: [message returned by 99minds]
Description: 99minds could not create the customer from the iPaaS.com record. The message includes the customer's email (when available) and the reason 99minds returned. 99minds requires a valid email address to create a customer.
Resolution: Confirm the customer has a valid email address (required by 99minds) and retry the transfer. If a customer with the same email already exists in 99minds, it is reused rather than recreated. If the failure persists, review the specific reason 99minds returned in the message and correct the field it names.
Customer update rejected by 99minds
99MN-EXTN-1007 - Customer update failed for [email]: [message returned by 99minds]
Description: 99minds could not update the customer from the iPaaS.com record. The message includes the customer's email (when available) and the reason 99minds returned.
Resolution: Review the reason 99minds returned and confirm the customer's fields — in particular a valid email — meet 99minds' requirements, then retry.
Existing customer could not be linked by email
99MN-BIZL-1002 - Unable to dynamically link to an existing 99minds customer using the email address. This may result in duplicate customer records.
Description: A customer with this email already existed, and the integration attempted to link the 99minds and iPaaS.com records so the transfer would update the existing customer rather than create a new one. The link could not be confirmed, so a duplicate may be created. (This same check applies to customers transferring in either direction.)
Resolution: Check whether a customer with this email already exists on both sides. If a duplicate was created, your MiSP can reconcile the external-ID link so future transfers update the correct customer.
99minds Customer TO iPaaS.com
Customer skipped for tier change webhook
99MN-BIZL-1001 - Skipping customer transfer. Customer creation is not supported for tier change webhooks.
Description: A tier-change event arrived for a customer that does not yet exist in iPaaS.com. By design, the integration does not create a brand-new customer from a tier-change event — the customer is transferred to iPaaS.com later, when the tier is assigned to the 99minds customer through the normal customer flow.
Resolution: No action is required. The customer and their tier will transfer through the standard Customer flow. If you expected this customer to already exist in iPaaS.com, confirm the customer has been synced, or contact your MiSP to review the mapping.
Prerequisite tier category could not be created
99MN-EXTN-1010 - Unable to create the 99minds Tier as a customer category in iPaaS.com. This prevented the customer from transferring.
Description: The customer has a 99minds tier that is not yet linked to an iPaaS.com Customer Category. The integration attempted to create that Customer Category first and it failed, so the customer did not transfer.
Resolution: Look for the tier/Customer Category transfer's own error in the same activity log and resolve it first, then retry the customer. If the tier-to-category mapping needs adjustment, contact your MiSP.
99minds Loyalty Card Transaction TO iPaaS.com
Prerequisite customer could not be created for transaction
99MN-EXTN-1011 - Unable to create the customer required for this transaction. This prevented the transaction from transferring.
Description: A loyalty card transaction references a customer that does not yet exist in iPaaS.com. The integration attempted to create that customer first and it failed, so the transaction did not transfer.
Resolution: Look for the customer transfer's own error in the same activity log and resolve it first, then retry the transaction. If the customer mapping needs adjustment, contact your MiSP.
Prerequisite customer could not be updated for transaction
99MN-EXTN-1012 - Unable to update the customer required for this transaction. This prevented the transaction from transferring.
Description: A loyalty card transaction references a customer that already exists in iPaaS.com. The integration attempted to update that customer first and it failed, so the transaction did not transfer.
Resolution: Look for the customer transfer's own error in the same activity log and resolve it first, then retry the transaction. If the customer mapping needs adjustment, contact your MiSP.
Existing transaction could not be linked by tracking number
99MN-BIZL-1004 - Unable to dynamically link to an existing iPaaS.com Transaction using the Tracking Number. This may result in duplicate transaction records.
Description: iPaaS.com already had a transaction with this tracking number, and the integration attempted to link the two records so the transfer would update the existing transaction rather than create a new one. The link could not be confirmed, so a duplicate may be created.
Resolution: Check whether a transaction with this tracking number already exists in iPaaS.com. If a duplicate was created, your MiSP can reconcile the external-ID link so future transfers update the correct transaction.
Add 99minds Order Completed Workflow FROM iPaaS.com
Prerequisite customer could not be created
99MN-EXTN-1008 - Unable to create the customer required for this order. This prevented the order from transferring.
Description: Before an order can transfer to 99minds, its customer must exist in 99minds. The integration attempted to create that customer first and the customer transfer failed, so the order did not transfer.
Resolution: Look for the customer transfer's own error in the same activity log and resolve it first — most often a missing or invalid customer email. Once the customer transfers successfully, retry the order. If the customer mapping needs adjustment, contact your MiSP.
Add/Update 99minds Tier TO iPaaS.com
Existing customer tier could not be linked by name
99MN-BIZL-1003 - Unable to dynamically link to an existing Customer Tier using the tier name. This may result in duplicate Tier records.
Description: iPaaS.com already had a Customer Category matching this 99minds tier name, and the integration attempted to link the two so the transfer would update the existing category rather than create a new one. The link could not be confirmed, so a duplicate may be created.
Resolution: Check whether a Customer Category matching this tier already exists in iPaaS.com. If a duplicate was created, your MiSP can reconcile the external-ID link so future transfers update the correct category.
Related Documents
Setup & Reference
Mapping Documentation