PayFabric from iPaaS.com Company Mapping Documentation

PayFabric customer profiles can be created and updated from iPaaS.com companies through manual sync or automatic outbound transfers. PayFabric has no separate company entity, so a company is written to PayFabric as a customer profile (identified by a COMP-prefixed CustomerId), including the company's billing and shipping addresses.

ID Format

Manual Sync ID Format

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

External ID Format

After a successful transfer, iPaaS.com records the PayFabric CustomerId (the COMP-prefixed value) as the external id on a dedicated external-id record, which routes subsequent updates to the same PayFabric record. On a first sync with no external-id record, the integration matches an existing PayFabric customer by email and links to it rather than creating a duplicate.

Deleted Record Support

Outbound delete is not supported for this collection. The Company model's delete operation is not implemented, delete mappings are not included in the default templates, and deleting a company 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.

Mapping Collection Status

Status: Enabled

Trigger Events: Company Create, Company Update (subscribed under Outbound Data Flows as company/created and company/updated). Manual Sync is also available at any time.

Duplicate or Conflicting Mappings

Add/Update PayFabric Customer FROM iPaaS.com also writes to PayFabric customers. Companies are written with a COMP-prefixed CustomerId, which keeps them distinct from customer records that use the raw customer Id.

Collision handling

Before creating the record, the integration checks the email; if a PayFabric customer with that email already exists, it 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 Company Address FROM iPaaS.com — writes the company's billing and shipping addresses onto the PayFabric customer profile. It is invoked as part of this parent's transfer.

System Caveats

PayFabric Caveats

The COMP-prefixed 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 company 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 company/created and company/updated outbound triggers under Outbound Data Flows. See the PayFabric Installation Instructions for the full walkthrough.

Integration Flow

A company is created or updated in iPaaS.com, or is manually synced by Company Id.
The integration resolves whether the company already exists in PayFabric — first by the external-id link, otherwise by matching the email address.
The company is created or updated as a PayFabric customer via POST /receivables/sync/api/{PortalName}/api/customers, using a COMP-prefixed CustomerId.
The company'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 Company FROM iPaaS.com

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

Mapping Type	Source Field (iPaaS.com)	Destination Field (PayFabric)	Description
Dynamic Formula	`return "COMP" + Id;`	CompanyId	Required. The PayFabric customer identifier for the company: `COMP` plus the iPaaS.com company Id (for example, `COMP4521`). The prefix keeps companies distinct from customer records.
Field	Name	Name	Recommended. The company name.
Field	EmailAddress	Email	A single valid email address (maximum 255 characters). Also used to match an existing PayFabric customer.
Field	TaxIdNumber	TaxExemptNumber	Optional. The company's tax-exempt number.
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 company's new email.
Static	`"No"`	SendEmail	Optional. Valid values Yes and No (maximum 3 characters).
Static	`"Active"`	Status	Optional. Valid values Active, Inactive, Deleted (maximum 50 characters).

Add/Update PayFabric Company Address FROM iPaaS.com

Description. Writes the company'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 company 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 (see formula below)	Name	The address contact name.
Field	IsPrimaryBilling	IsDefaultBilling	Designates the billing address (same precedence rules as the customer address collection).
Field	IsPrimaryShipping	IsDefaultShipping	Designates the shipping address (same precedence rules).

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;

Error Handling

"PayFabric Company could not be created" — Appears in the iPaaS.com Error Logs when PayFabric rejects the company create. Confirm the CompanyId formula resolved and the portal credentials are valid.
"PayFabric Company could not be updated" — Appears when PayFabric rejects the company update. Verify the record still exists in PayFabric and that the mapped values are within the documented field limits.

Testing & Validation

Test Scenarios

Create a new company in iPaaS.com and verify a PayFabric customer profile appears with a COMP-prefixed CustomerId, the company name, and email.
Update the company name or email and verify the change propagates to the same PayFabric record.
Re-send an unchanged company and confirm no duplicate is created.
Manually sync a company by its iPaaS.com Company Id and confirm success.
Create a company with billing and shipping addresses and verify both appear on the PayFabric customer profile.

Validation Checklist

The CompanyId formula resolves to a unique COMP-prefixed value.
Email is a single valid address.
Currency has been reviewed and set to the correct code.

Additional Notes

Because companies and customers both become PayFabric customers, review the Add/Update PayFabric Customer FROM iPaaS.com collection alongside this one when defining the source of truth.