Skip to main content

PayFabric Error Messages

Common PayFabric integration error messages in iPaaS.com, what each one means, and how to resolve it.

Overview

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. Each entry carries a stable error code you can search for on this page, the message text as it appears in the log, what the error means, and how to resolve it. Errors appear under Dashboard / Integration Monitoring / Error Logs.

Some resolutions reference your Managed Integration Service Provider (MiSP) — the partner who configured and maintains your PayFabric integration, including its mappings, presets, and record reconciliation. Where a resolution goes beyond what you can adjust yourself, your MiSP is the first point of contact.

iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.

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

Error Collection

Customer and Company (FROM iPaaS.com)

Could not link customer by email

PYFB-BIZL-1001 - Unable to dynamically link to existing PayFabric customer using email address {email address}. This may result in duplicate customer records.

  • Description: During a customer transfer with no external-id link yet, the integration matched an existing PayFabric customer by the email address shown and attempted to link it, but PayFabric returned a different customer than the one matched, so the link could not be completed. Continuing may create a duplicate customer.

  • Resolution: In PayFabric, find the customer records that share the email address shown and consolidate them so a single record owns that email, then re-sync the customer — the transfer will link to it. Reconciling existing duplicate customer records is owned by your MiSP; have them clean up the duplicates in PayFabric if you cannot.

Could not link company by email

PYFB-BIZL-1002 - Unable to dynamically link to existing PayFabric customer company using email address {email address}. This may result in duplicate company records.

  • Description: The company transfer matched an existing PayFabric customer (company) by the email address shown and attempted to link it, but PayFabric returned a different record than the one matched, so the link could not be completed. Companies are stored as PayFabric customers with a COMP-prefixed id.

  • Resolution: In PayFabric, find the COMP-prefixed records that share the email address shown and consolidate them so a single record owns that email, then re-sync the company. Reconciling existing duplicate company records is owned by your MiSP; have them clean up the duplicates in PayFabric if you cannot.

Customer could not be created

PYFB-EXTN-1002 - PayFabric Customer could not be created

  • Description: PayFabric rejected the customer create request. Common causes are a missing required CustomerId or invalid credentials. The full PayFabric detail is included in the Error Logs entry.

  • Resolution: Read the PayFabric detail in the log entry, then confirm the customer Id is mapped and the Integration Key and Integration Password are correct. Correct the field PayFabric reported and re-sync the customer. If the detail points to a customer mapping you cannot adjust, your MiSP owns that mapping and can correct it.

Customer could not be updated

PYFB-EXTN-1003 - PayFabric Customer could not be updated

  • Description: PayFabric rejected the customer update request. The full PayFabric detail is included in the Error Logs entry.

  • Resolution: Read the PayFabric detail in the log entry, confirm the customer resolves to an existing PayFabric record, and correct the field PayFabric reported. Re-sync the customer. If the detail points to a customer mapping you cannot adjust, your MiSP owns that mapping and can correct it.

Company could not be created

PYFB-EXTN-1004 - PayFabric Company could not be created

  • Description: PayFabric rejected the company create request. Companies are stored as PayFabric customers with a COMP-prefixed id. The full PayFabric detail is included in the Error Logs entry.

  • Resolution: Read the PayFabric detail in the log entry, confirm the company resolves to a unique COMP-prefixed id, and correct the field PayFabric reported. Re-sync the company. If the detail points to a company mapping you cannot adjust, your MiSP owns that mapping and can correct it.

Company could not be updated

PYFB-EXTN-1005 - PayFabric Company could not be updated

  • Description: PayFabric rejected the company update request. The full PayFabric detail is included in the Error Logs entry.

  • Resolution: Read the PayFabric detail in the log entry, confirm the company resolves to an existing COMP-prefixed record, and correct the field PayFabric reported. Re-sync the company. If the detail points to a company mapping you cannot adjust, your MiSP owns that mapping and can correct it.

Invoice (FROM iPaaS.com)

Customer prerequisite could not be created

PYFB-EXTN-1009 - Unable to create customer. This will prevent the transfer of the order.

  • Description: An invoice transfer needs its customer in PayFabric first. The integration tried to create the customer as a prerequisite and PayFabric rejected it, so the invoice was not transferred.

  • Resolution: Resolve the underlying customer error first — its own entry (a "Customer could not be created" error) is logged alongside this one; see the Customer and Company section. Once the customer transfers successfully, re-sync the invoice.

Company prerequisite could not be created

PYFB-EXTN-1010 - Unable to create company. This will prevent the transfer of the order.

  • Description: An invoice transfer needs its company in PayFabric first. The integration tried to create the company as a prerequisite and PayFabric rejected it, so the invoice was not transferred.

  • Resolution: Resolve the underlying company error first — its own entry (a "Company could not be created" error) is logged alongside this one; see the Customer and Company section. Once the company transfers successfully, re-sync the invoice.

Could not link to existing transaction

PYFB-BIZL-1003 - Unable to dynamically link to an existing transaction {transaction ID}. This may result in duplicate transaction records.

  • Description: The integration matched the invoice to an existing PayFabric transaction and attempted to link it, but PayFabric returned a different transaction than the one matched, so the link could not be completed. Continuing may create a duplicate transaction.

  • Resolution: Confirm the transaction shown was previously transferred and that its external-id link exists in iPaaS.com. If a duplicate transaction has appeared in PayFabric, reconciling it is owned by your MiSP; have them consolidate it so the correct transaction is linked.

Payment does not apply to an invoice

PYFB-NFND-1001 - Payment {payment ID} does not apply to any invoice.

  • Description: The payment shown is not associated with any invoice in PayFabric, so it cannot be processed against one.

  • Resolution: In PayFabric, apply the payment shown to the intended invoice, then re-sync. If the payment should already be applied and is not, your MiSP can verify the payment-to-invoice application in PayFabric.

No payment found for the invoice

PYFB-NFND-1002 - No payment exists for the requested invoice {invoice ID}.

  • Description: The integration expected a payment on the invoice shown (for example, during a refund) but none was found in PayFabric.

  • Resolution: Confirm the invoice shown has an approved payment in PayFabric before initiating a refund, then re-sync. If a payment exists but is not found, your MiSP can verify it is applied to that invoice.

Invoice could not be created

PYFB-EXTN-1006 - PayFabric Invoice could not be created

  • Description: PayFabric rejected the invoice create request. Common causes are an invalid InvoiceType, an unresolved customer or company, or a field exceeding PayFabric's limits (for example, line-item codes are capped at 50 characters). The full PayFabric detail is included in the Error Logs entry.

  • Resolution: Read the PayFabric detail in the log entry, then confirm the transaction Type maps to a valid PayFabric InvoiceType, the customer or company is linked, and field lengths are within limits. Correct the field PayFabric reported and re-sync the invoice. If the detail points to an invoice mapping you cannot adjust, your MiSP owns that mapping and can correct it.

Invoice could not be updated

PYFB-EXTN-1007 - PayFabric Invoice could not be updated

  • Description: PayFabric rejected the invoice update request. The full PayFabric detail is included in the Error Logs entry.

  • Resolution: Read the PayFabric detail in the log entry, confirm the invoice resolves to an existing PayFabric record, and correct the field PayFabric reported. Re-sync the invoice. If the detail points to an invoice mapping you cannot adjust, your MiSP owns that mapping and can correct it.

Refund (FROM iPaaS.com)

Transaction Key required for refund

PYFB-VALD-1001 - 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. If you are unsure of the source value for this payment, your MiSP can confirm where the Transaction Key comes from.

Could not link to existing transaction payment

PYFB-BIZL-1004 - Unable to dynamically link to an existing transaction payment {payment ID}. This may result in duplicate transaction payment records.

  • Description: The integration matched the refund to an existing PayFabric payment and attempted to link it, but PayFabric returned a different payment than the one matched, so the link could not be completed. Continuing may create a duplicate payment record.

  • Resolution: Confirm the original payment shown was transferred and that its link exists in iPaaS.com. If a duplicate payment has appeared in PayFabric, reconciling it is owned by your MiSP; have them consolidate it so the correct payment is linked.

Refund was not approved

PYFB-EXTN-1008 - {PayFabric refund decline reason}

  • Description: PayFabric processed the refund request but did not approve it. The message shown is the reason PayFabric returned (for example, an amount exceeding the refundable balance, or a missing Device credential).

  • Resolution: Read the reason PayFabric returned in the message. If it concerns the amount, confirm the refund does not exceed the payment's refundable balance. If it concerns credentials, verify the Device ID and Device Password. Correct the cause and re-initiate the refund. If the reason concerns the original payment, your MiSP can review the refund against it in PayFabric.

Invoice Payment (TO iPaaS.com)

Payment method does not exist in iPaaS.com

PYFB-NFND-1003 - This payment method {payment 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. The payment method name shown is the one PayFabric returned.

  • Resolution: Create the payment method in iPaaS.com using the exact name shown in the message, then re-sync the payment. If you are unsure which payment methods PayFabric uses, your MiSP can confirm the full set so they can be created ahead of time.

PayFabric API and Authentication

PayFabric returned an error

PYFB-EXTN-1001 - {PayFabric error detail}

  • Description: PayFabric rejected a request. The integration surfaces PayFabric's own error detail (code, message, and any additional data) in the Error Logs entry.

  • 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. If the detail points to the contents of the request, your MiSP can review the mapping that produced it.

Authentication failed

PYFB-AUTH-1001 - Failed to retrieve access token from PayFabric using Token API. Please see logs for more details.

  • 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. If the values are correct in iPaaS.com, confirm the same credentials in the PayFabric portal; your MiSP can help verify the portal-side setup.

Related Documents

Related Articles
Did this answer your question?