Change Requests are vital to managing and updating your account information within the Payrix Portal. The term “Change Requests” refers to an entity adding or updating their bank account information. This entity is required to must submit relevant documentation to support the validity of its new bank account info.
As this process requires manual review from a Payrix or Facilitator-level risk analyst, it cannot be instantly approved, so submissions made to add or change a bank account have been compiled into a set of easy-to-use Portal pages for each level of user to keep track or take action on their bank account change requests.
Automation of “manual” review for approval is anticipated to be integrated in early 2024.
This guide will provide an overview of Change Requests, their importance, and how they impact different user levels.
For Referrers & Merchants
Referrers and Merchants often need to make changes to their bank account information. The Change Request process allows added or changed account information to be submitted with documentation to support the change during risk analysis.
Referrers & Merchants can:
...
...
information.
This guide will provide an overview of Change Requests, their importance, and how they impact different user levels.
For Referrers & Merchants
Referrers and Merchants often need to make changes to their bank account information. The Change Request process allows added or changed account information to be submitted with documentation to support the change during risk analysis.
Referrers & Merchants can:
...
Note: Referrers can submit Change Requests on behalf of Merchants. This includes:
Updating bank account information from the Banking tab of the Merchant’s Profile page.
While logged in as the Merchant, update bank account information from the Banking tab of the Merchant’s Portal Account Profile.
Submitting an API call to the
/changeRequestsendpoint associated with the Merchant’s Login ID.
For Facilitators
Facilitators play a crucial role in handling change requests. Since Facilitators take on the responsibility of managing and mitigating their own risk, the Change Request management process provides full visibility of changes happening to bank accounts within their portfolio, to prevent risk hazards, such as money laundering, due to unverified or unauthorized bank accounts being added without notification.
...
Front End User Interface for Facilitators & Referrers
We recommend that Facilitators and Referrers with whitelabeled Portals and custom sites take additional steps to map and configure their front-end user interface (UI) to maximize user (Merchant) transparency and minimize communication times. Read more about these specific tips below:
| Expand | ||
|---|---|---|
| ||
We recommend Facilitators that use the Change Requests workflow above with an API integration to incorporate the following into your front-end user interface development: Tip: Display Change Request Messages
Real-Time Status Updates
Communicate Decline Reasons
|
Prevent Funding to an Existing Bank Account
To prevent funds from being sent to an existing account while the change request is being reviewed and approved, either as an optional feature for merchants to choose when submitted submitting the bank change or as the default process for your software
...
The Merchant’s bank account being has been closed by their bank due to reported fraudulent activity.
The Merchant’s bank account was closed by the merchant prior to before the change request being approved.
The Merchant added incorrect bank account information by mistake that they do not want to use.
...
| Info |
|---|
To learn more about the specifics of adding or updating a bank account, see our Account Maintenance articles: |
The processes outlined below will outline how to submit a Change Request to update your or your Merchant’s bank account information.
...
a note added to the Referrer or Merchant account, and;
an email to the user that submitted the Change Request with more detail explaining the review result and reason.
Read more about Declines below.
...
| title | More on Declines |
|---|
Decline Responses
When a submission is Declined, a reason and accompanying note will be added to your entity account by the reviewer. Declines can occur for one of the following reasons:
Decline Reason | Description |
|---|---|
Unable to validate | The information provided doesn't allow risk analysts to validate your information. |
No Response | Analysts have followed up with additional questions and received no response. |
Invalid Document | The document provided for review was not sufficient. |
Unable to read | The document provided was unreadable. |
Expired Document | The document provided has expired. |
Other | Custom reason, filled out by reviewing Risk Analyst as needed. |
These declines will be accompanied by a note added to your account from the risk reviewer.
...
View Your Pending Change Requests
| Anchor | ||||
|---|---|---|---|---|
|
...
| Expand | ||
|---|---|---|
| ||
From the Change Requests Queue, you can:
|
...
| Info | ||
|---|---|---|
You can also view previously declined Change Requests by clicking the Declined filter on the Change Requests tab. | ||
| Expand | ||
| ||
Declines can occur for one of the following reasons: | ||
Decline Reason | Description | |
Unable to validate | The information provided doesn't allow risk analysts to validate your information. | |
No Response | Analysts have followed up with additional questions and received no response. | |
Invalid Document | The document provided for review was not sufficient. | |
Unable to read | The document provided was unreadable. | |
Expired Document | The document provided has expired. | |
Other | Custom reason, filled out by reviewing Risk Analyst as needed. |
...
Test Bank Account Change Requests in the Sandbox Environment
| Anchor | ||||
|---|---|---|---|---|
|
...