PayFabric Error Messages

This article catalogs the error messages a subscriber may encounter in the iPaaS.com Error Logs while running the PayFabric integration, grouped by transfer flow, with what each error means and how to resolve it. Errors appear under Dashboard / Integration Monitoring / Error Logs.

Supported Flows

Customer and Company (FROM iPaaS.com)
Invoice (FROM iPaaS.com)
Refund (FROM iPaaS.com)
Invoice Payment (TO iPaaS.com)
PayFabric API and Authentication

Customer and Company (FROM iPaaS.com)

Could not link customer by email

Unable to dynamically link to existing PayFabric customer using email address. This may result in duplicate customer records.

Description: During a customer transfer with no external-id link yet, the integration tried to match an existing PayFabric customer by email and could not complete the link.
Resolution: Confirm the customer's email is valid and matches the intended PayFabric customer. If the customer already exists in PayFabric under a different email, link or correct it so future transfers update the right record. If the problem persists, contact iPaaS.com Product Support.

Could not link company by email

Unable to dynamically link to existing PayFabric customer company using email address. This may result in duplicate company records.

Description: The company transfer could not match an existing PayFabric customer (company) by email.
Resolution: Confirm the company email is valid. Companies are stored as PayFabric customers with a COMP-prefixed id; verify no conflicting record exists. Contact iPaaS.com Product Support if it recurs.

Customer could not be created or updated

PayFabric Customer could not be created (or PayFabric Customer could not be updated)

Description: PayFabric rejected the customer write. Common causes are a missing required CustomerId or invalid credentials.
Resolution: Ensure the customer Id is mapped and the Integration Key and Integration Password are correct. Review the full error in the Error Logs for the PayFabric detail, then retry. Contact iPaaS.com Product Support if it persists.

Company could not be created or updated

PayFabric Company could not be created (or PayFabric Company could not be updated)

Description: PayFabric rejected the company write.
Resolution: Confirm the company resolves to a unique COMP-prefixed id and the credentials are valid. Review the error detail and retry; contact iPaaS.com Product Support if needed.

Invoice (FROM iPaaS.com)

Customer or company prerequisite failed

Unable to create customer. This will prevent the transfer of the order. (or Unable to create company. This will prevent the transfer of the order.)

Description: An invoice transfer needs its customer or company in PayFabric first. The integration tried to create it as a prerequisite and could not, so the invoice was not transferred.
Resolution: Resolve the underlying customer/company error (see the Customer and Company section), then re-sync the invoice.

Could not link to existing transaction

Unable to dynamically link to an existing transaction. This may result in duplicate transaction records.

Description: The integration could not link the invoice to its existing PayFabric record, which risks creating a duplicate.
Resolution: Confirm the invoice was previously transferred and its external-id link exists. Contact iPaaS.com Product Support if duplicates appear.

Payment does not apply to an invoice

This payment does not apply to any invoice.

Description: A payment on the transaction is not associated with any invoice, so it cannot be processed against one.
Resolution: Ensure the payment references a valid invoice before transferring.

No payment found for the invoice

No payment exists for the requested invoice.

Description: The integration expected a payment on the invoice (for example, during a refund) but none was found.
Resolution: Confirm the invoice has an approved payment in PayFabric before initiating a refund.

Invoice could not be created or updated

PayFabric Invoice could not be created (or PayFabric Invoice could not be updated)

Description: PayFabric rejected the invoice write. Common causes are an invalid InvoiceType, an unresolved customer/company, or a field exceeding PayFabric's limits.
Resolution: Confirm the transaction Type maps to a valid PayFabric InvoiceType, the customer/company is linked, and field lengths are within limits (for example, line-item codes are capped at 50 characters). Review the error detail and retry.

Refund (FROM iPaaS.com)

Transaction Key required for refund

Transaction Key is required when IsRefundable is true.

Description: A payment is flagged refundable but has no Transaction Key, so the refund cannot be processed.
Resolution: Populate the Transaction Key custom field on the payment in iPaaS.com before initiating the refund.

Could not link to existing transaction payment

Unable to dynamically link to an existing transaction payment. This may result in duplicate transaction payment records.

Description: The integration could not link the refund to its existing PayFabric payment record.
Resolution: Confirm the original payment was transferred and its link exists; contact iPaaS.com Product Support if duplicate payment records appear.

Invoice Payment (TO iPaaS.com)

Payment method does not exist in iPaaS.com

This payment method [method] does not exist and needs to be created manually in iPaaS.com.

Description: A payment polled from PayFabric uses a payment method that has not been created in iPaaS.com, so the payment cannot be recorded. [method] is the PayFabric payment method name.
Resolution: Create the payment method in iPaaS.com using the exact name shown in the message, then re-sync the payment.

PayFabric API and Authentication

PayFabric returned an error

PayFabric error responses appear in the Error Logs with the detail PayFabric returned.

Description: PayFabric rejected a request. The integration surfaces PayFabric's own error detail in the Error Logs.
Resolution: Read the returned detail. Frequent causes are invalid credentials (verify the Integration Key and Integration Password), or refunds attempted without the Device ID and Device Password. Correct the cause and retry; contact iPaaS.com Product Support if the detail is unclear.

Authentication failed

401 Unauthorized — PayFabric rejected the credentials.

Description: The integration could not obtain a PayFabric session token, typically because the Portal Name, Integration Key, or Integration Password is incorrect, or the PayFabric Integration Method is not set to API only.
Resolution: Verify the Portal Name, Integration Key, and Integration Password, and confirm the PayFabric Integration Method is API only. See Connections and Settings.