PayFabric Connections and Settings
Integrate iPaaS.com with PayFabric to synchronize customers, companies, invoices, payments, and refunds between iPaaS.com and the PayFabric Receivables and Payment services.
Prerequisites
Before configuring the subscription in iPaaS.com, gather the following from your PayFabric account, and set the PayFabric Integration Method to API only:
Portal Name — your company's PayFabric account (tenant) identifier. Found under Receivables > Settings > Company.
Integration Key — the API key used to authenticate to the PayFabric Receivables service. Found under Receivables > Settings > Integration > Connection.
Integration Password — paired with the Integration Key. Found under Receivables > Settings > Integration > Connection.
Device ID and Device Password — identify the payment device (gateway account) used for refunds and voids. Found under PayFabric > Settings (Device Management). The Device Password is shown once when the device is created; if it is lost, a new device must be created. These are only needed if you will process refunds or voids from iPaaS.com.
Configuration Details
API URL — the PayFabric instance URL. Use
https://sandbox.payfabric.comfor the sandbox/test environment; the production URL is provided by PayFabric for your account. The URL is instance-specific.Portal Name, Integration Key, and Integration Password — the Receivables Sync credentials gathered above.
Device ID and Device Password — the Referenced Transaction (Payment/Gateway) credentials gathered above, required for refunds and voids.
Configure Subscription Settings
Field | Description | Required | Example |
API URL | The PayFabric instance URL (sandbox or production). | Yes |
|
Portal Name | The PayFabric account (tenant) identifier used in API calls. | Yes |
|
Integration Key | The Receivables Sync API key. | Yes | (from PayFabric) |
Integration Password | Paired with the Integration Key for Receivables Sync authentication. | Yes | (from PayFabric) |
Device ID | Identifies the PayFabric payment device for refunds and voids. | Conditional — required only to process refunds or voids | (from PayFabric) |
Device Password | Paired with the Device ID for the Payment/Gateway service. | Conditional — required only to process refunds or voids | (from PayFabric) |
Invoice Poll Search Days | The look-back window, in days before the current time, used when polling PayFabric for changed invoice payments. Applied on the first poll or whenever there is no recorded last-poll date. Defaults to 5 days when left blank. | No |
|
Authentication Methods
PayFabric uses two credential sets, because the integration calls two PayFabric services:
Receivables Sync service (customers, companies, invoices, payments) — iPaaS.com uses the Portal Name, Integration Key, and Integration Password to obtain a session token, then uses that token for customer, invoice, and payment calls. There is no separate OAuth app to register; the token is requested automatically using these credentials.
Payment / Gateway service (refunds and voids) — authenticated with the Device ID and Device Password. If these are not configured, customer and invoice synchronization still works, but refunds and voids do not.
Set the PayFabric Integration Method to API only so these credentials can authenticate.
Initialization Support
Currently, initialization (bulk data import on first connect) is not supported for PayFabric in iPaaS.com. Data synchronization and mappings are configured and run as records are created, updated, or polled. For a large initial load, use the supported bulk sync using Postman approach.
Throttling
The subscription's throttle fields — API Throttle Limit, API Throttle Seconds, and Concurrent Connections — control how many API requests run concurrently and how often they are allowed; they are pre-populated by the integration's settings and protect PayFabric from being overwhelmed. In addition, Concurrent Batch Executions bounds how many transfers the integration runs simultaneously within a batch. Adjust these only if you understand the impact on throughput; the defaults are suitable for most subscriptions.