Payrix
Overview
Below is a summary of the connection key facts to support your integration.
| Category | |
|---|---|
| Processor Type | Platform Processor |
| Preczn Enumeration | Payrix |
| Documentation | Payrix Resource Center |
Supported Features
The following features are supported for this connection:
Payment Methods
| Payment Method | Supported |
|---|---|
| Credit Cards | ✅ Yes |
| ACH (Direct Debit) | ✅ Yes |
| Apple Pay on the Web | ✅ Yes |
Payment Data
| Data Type | Supported |
|---|---|
| Country & Currency Codes | ✅ Yes |
| Metadata | ❌ No |
| Dynamic Statement Descriptors | ✅ Yes |
| CVV | ✅ Yes |
| AVS | ✅ Yes |
| Level II Data | ✅ Yes |
| Level III Data | ✅ Yes |
Transaction Import
| Import Capability | Supported |
|---|---|
| One-Time Transaction Import | ✅ Yes |
| Continuous Transaction Import | ✅ Yes |
Merchant Import
| Import Capability | Supported |
|---|---|
| One-Time Merchant Import | ✅ Yes |
| Continuous Merchant Import | ✅ Yes |
Merchant Onboarding
| Features | Supported |
|---|---|
| Merchant Onboarding | ✅ Yes |
| Merchant RFI Remediation | ✅ Yes |
Adding Platform Credentials
For details on how to configure platform connections, first read the Connection Configuration guide.
This connection supports the following fields for connection configuration:
| Preczn Field | Required | Notes |
|---|---|---|
| API Key | Required | Please retrieve the API key from the developer section of the payrix portal. Due to hierarchal nature of Payrix Logins, we recommend the parent user for your organization retrieve the key so that all child accounts can be accessed |
| Default Group | Optional | When provided, these will become the default group(s) to which merchants are assigned upon being onboarded to Payrix. This field supports adding multiple groups to suit specific use-cases. As this only affects merchants boarded after a group is applied, all other group management tasks should be carried out within the Payrix Portal. |
| Default User | Optional | The portal access permissions of the default user will be applied to all newly created users. (Payrix will assist you in creating a default user template for instances requiring your merchants to have Payrix Portal access.) |
Adding Merchant Credentials
To establish an API connection with Payrix for a merchant who already has a relationship with them, you will need to provide the following credentials:
| Payrix Value | Preczn API value | Notes |
|---|---|---|
| Payrix Merchant ID | mid | Please note that the entity ID is not needed, only the merchant ID |
Transaction Integration
Channel Field Use
In addition to standard transaction API request properties, Payrix offers an optional field, channel, which allows a string up to 1000 characters in length.
This field is only available on initial transactions, i,e. Sale or Authtransactions. Subsequent transactions against the initial transaction are not editable and will retain the same value of the initial transaction.
The channel field is surfaced in the Payrix Portal and can be used at your platform's discretion to associate additional information to a given Sale or Auth transaction.
Merchant Onboarding
asdf
Merchant RFI Remediation
At present, Payrix's underwriting team creates Request For Information (RFI) on a case by case basis via email. Typically, Payrix's underwriting asks are included in an email as a bulleted list, with the Merchant's name and Payrix MID in the subject line.
You may create a forwarding rule from your organizations domain to forward these emails to[email protected]. Preczn will then parse the email, and attach the action to the appropriate merchant in Preczn provided a matching Payrix MID and standard RFI email format is followed.
In addition to displaying the RFI on your merchant's profile in the Preczn dashboard, we also will return the list via api or webhook as the actionDescription object for you to consume and present in your application.
Review and Approve RFIs
Due to the inconsistent nature of email, Preczn strongly advises reviewing and "approving" each RFI message prior to presenting required actions to your merchants- this will ensure your merchant is presented with clear, actionable requirements to streamline the onboarding process. Preczn uses the boolean object
actionDescriptionReviewedto indicate that an actionDescription has been reviewed.
You may choose to have an RFI form be created upon your merchants acknowledgement of a required action, this will allow the merchant to make the necessary updates and can be configured to automatically re-transmit changes to Payrix upon saving of the RFI form. Preczn will then automatically send an email to the Payrix risk department notifying them the RFI has been fulfilled and new or updated data is ready for their review.
Updated 21 days ago