PayFabric from iPaaS.com Customer Mapping Documentation

PayFabric customer profiles can be created and updated from iPaaS.com customers through manual sync or automatic outbound transfers. When a customer is created or updated in iPaaS.com, the integration writes a matching customer profile to PayFabric through the PayFabric Receivables Sync API, including the customer's billing and shipping addresses.

ID Format

Manual Sync ID Format

On the iPaaS.com Manual Sync page, enter the iPaaS.com Customer Id of the record to transfer (for example, 482913).

External ID Format

After a successful transfer, iPaaS.com records the PayFabric CustomerId as the external id on a dedicated external-id record. Subsequent transfers use that link to route updates to the same PayFabric customer. On a first sync where no external-id record exists yet, the integration matches an existing PayFabric customer by email address and links to it rather than creating a duplicate.

Deleted Record Support

Outbound delete is not supported for this collection. The Customer model's delete operation is not implemented, delete mappings are not included in the default templates, and deleting a customer in iPaaS.com does not remove the corresponding customer in PayFabric.

Custom Field Support

This collection does not map custom fields. PayFabric customer profiles expose no subscriber-mappable custom fields, so all values are written through the standard fields below.

Mapping Collection Status

Status: Enabled

Trigger Events: Customer Create, Customer Update (subscribed under the subscription's Outbound Data Flows as customer/created and customer/updated). Manual Sync is also available at any time.

Duplicate or Conflicting Mappings

Add/Update PayFabric Company FROM iPaaS.com also writes to PayFabric customers — PayFabric has no separate company entity, so iPaaS.com companies are created as PayFabric customers with a COMP-prefixed CustomerId.

Collision handling

Before creating a customer, the integration checks the email address; if a PayFabric customer with that email already exists, the existing customer is updated instead of creating a duplicate. Decide the source of truth for customer versus company records before enabling both collections, and confirm no customer uses a COMP-prefixed identifier.

Supported Child Collections

Add/Update PayFabric Customer Address FROM iPaaS.com — writes the customer's billing and shipping addresses onto the PayFabric customer profile. It is invoked as part of this parent's transfer.

System Caveats

PayFabric Caveats

CustomerId must be unique within the PayFabric tenant.
PayFabric permits duplicate email addresses across different CustomerIds; the integration's email check prevents duplicates on the iPaaS.com side.
PayFabric does not enforce address uniqueness.

iPaaS.com Caveats

The customer must exist in iPaaS.com before it can be transferred to PayFabric.

Setup Requirements

PayFabric Configuration

Set Integration Method to API only in the PayFabric portal.

iPaaS.com Configuration

Configure the subscription presets: API URL, Portal Name, Integration Key, and Integration Password.
For automatic transfers, subscribe to the customer/created and customer/updated outbound triggers under Outbound Data Flows. See the PayFabric Installation Instructions for the full walkthrough.

Integration Flow

A customer is created or updated in iPaaS.com, or is manually synced by Customer Id.
The integration resolves whether the customer already exists in PayFabric — first by the external-id link, otherwise by matching the email address.
The customer is created or updated in PayFabric via POST /receivables/sync/api/{PortalName}/api/customers.
The customer's addresses are written through the child collection during the same transfer.
The PayFabric CustomerId is recorded as the external id so later transfers update the same record.

Mappings

Add/Update PayFabric Customer FROM iPaaS.com

Description. Creates or updates the PayFabric customer profile from the iPaaS.com customer. This collection has no mapping filter — all customer records are processed.

Mapping Type	Source Field (iPaaS.com)	Destination Field (PayFabric)	Description
Field	Id	CustomerId	Required. The PayFabric customer identifier; must be unique within the PayFabric tenant.
Dynamic Formula	first + last name (see formula below)	Name	Recommended. The customer's full name.
Field	EmailAddress	Email	Recommended. A single valid email address (maximum 255 characters). Also used to match an existing PayFabric customer and prevent duplicates.
Static	`"US"`	Currency	Optional. PayFabric currency code (maximum 10 characters). Placeholder value — replace during implementation: ships as `US`; confirm the correct currency code for your PayFabric account.
Static	`"true"`	InvoiceEmailUpdate	Optional boolean. When `true`, PayFabric updates invoice emails with the customer's new email.
Static	`"No"`	SendEmail	Optional. Overrides PayFabric's customer-registration email. Valid values Yes and No (maximum 3 characters).
Static	`"Active"`	Status	Optional. PayFabric customer status. Valid values Active, Inactive, Deleted (maximum 50 characters).

Name formula:

string name = string.Empty;if(!string.IsNullOrWhiteSpace(FirstName))
name = FirstName;
if(!string.IsNullOrWhiteSpace(LastName))
name += " " + LastName;
if(!string.IsNullOrWhiteSpace(name))
return name;

Add/Update PayFabric Customer Address FROM iPaaS.com

Description. Writes the customer's billing and shipping addresses onto the PayFabric customer profile. This collection has no mapping filter — all address records are processed.

Mapping Type	Source Field (iPaaS.com)	Destination Field (PayFabric)	Description
Dynamic Formula	`Id`	AddressID	Required. The PayFabric address identifier, taken from the iPaaS.com customer address Id so updates apply to the existing address.
Field	Address1	Address1	The first address line.
Field	Address2	Address2	The second address line. Optional.
Field	Address3	Address3	The third address line. Optional.
Field	City	City	The city.
Field	Region	State	The state or region.
Field	PostalCode	Zip	The postal/ZIP code.
Field	Country	Country	The country.
Field	PhoneNumber	Phone	The contact phone number.
Dynamic Formula	first + last name, with parent fallback (see formula below)	Name	The address contact name.
Field	IsPrimaryBilling	IsDefaultBilling	Designates the billing address. If true and IsDefaultShipping is false, the address becomes the Billing Address when none is assigned; if both are false and no billing address is set, it is treated as the Primary Address.
Field	IsPrimaryShipping	IsDefaultShipping	Designates the shipping address, following the same precedence rules as IsDefaultBilling.

Address Name formula:

string name = string.Empty;if(!string.IsNullOrWhiteSpace(FirstName))
    name = FirstName;
if(!string.IsNullOrWhiteSpace(LastName))
    name += " " + LastName;
if(!string.IsNullOrWhiteSpace(name))
    return name;if(!string.IsNullOrWhiteSpace(Parent.FirstName))
    name = Parent.FirstName;
if(!string.IsNullOrWhiteSpace(Parent.LastName))
    name += " " + Parent.LastName;
if(!string.IsNullOrWhiteSpace(name))
    return name;

Error Handling

"PayFabric Customer could not be created" — Appears in the iPaaS.com Error Logs when PayFabric rejects the customer create. Confirm the required CustomerId is mapped and the portal credentials are valid.
"PayFabric Customer could not be updated" — Appears when PayFabric rejects the customer update. Verify the customer still exists in PayFabric and that the mapped values are within the documented field limits.

Testing & Validation

Test Scenarios

Create a new customer in iPaaS.com and verify a matching customer profile appears in PayFabric with the expected CustomerId, name, and email.
Update the customer's name or email in iPaaS.com and verify the change propagates to the same PayFabric customer (no duplicate is created).
Re-send an unchanged customer and confirm no duplicate customer is created in PayFabric.
Manually sync a customer by its iPaaS.com Customer Id and confirm success.
Create a customer with a billing and a shipping address and verify both addresses appear on the PayFabric customer profile with the correct default-billing/default-shipping designation.

Validation Checklist

CustomerId is mapped and unique.
Email is a single valid address.
Currency has been reviewed and set to the correct code for the PayFabric account.

Additional Notes

iPaaS.com companies are written to PayFabric as customers (with a COMP-prefixed CustomerId) through the separate Add/Update PayFabric Company FROM iPaaS.com collection; review both collections together when defining the source of truth for customer records.