Boarding Merchants to Connections
Summary
One of the value propositions of Preczn is the ease of which vertical SaaS platforms can onboard and underwrite their merchants to partner Fintech connections. Preczn is built to facilitate the collection, augmentation, evaluation, and distribution of Merchant data to meet your Connections' underwriting requirements.
At a high level, Preczn facilitates this onboarding operation by:
- Normalizing your Merchant data
- Tracking and identifying gaps in required data to onboard to a Connection
- Allowing various means of collecting the remain data and required terms and conditions for underwriting
- Transforming and submitting the Merchant data to the connection
- Tracking and communicating onboarding in a normalized format
- Identifying and resolving issues that may arise in the underwriting process
Over the next several sections we will address each step in how you can leverage Preczn to ease your Merchant onboarding experience.
Determining Required Merchant Data
When a merchant wants to establish business with Fintech service providers / Connections the merchant is required to submit data, documentation, and sign terms & conditions in order for the provider/connection to perform KYC and underwriting on the merchant.
As Platform with many merchants, you play a role is the collection and facilitation of these data, documents, and terms & conditions. However this can be a large endeavor requiring the understanding of what data is needed, available, and missing in order to confidently onboard the merchant.
Learn more about how Preczn not only keeps track of what data is required to onboard a merchant to a specific Connection, but also continually keeps track of required data here.
Onboarding Merchants to Connections
Need to add summary that includes...
- Managing Merchant Credentials in the Dashboard and via API
- Merchants with Existing Credentials
Merchant Connection Statuses
Preczn's Connection Statuses are fundamental to the management and utilization of various third-party payment processors and financial service providers.
As a unique feature of Preczn, it allows each of your merchants to establish and maintain connections with different service providers, all the while assigning each connection a distinct status.
These statuses provide a detailed and real-time representation of each connection's current condition.
Whether a connection has been newly configured, successfully established, is in the process of being updated, or is facing an error, the Connection Status reflects it all.
This not only allows Preczn to efficiently track and map the state of each connection for every merchant but also unifies what could be many different statuses across multiple different 3rd party providers.
Connection Statuses
Status | Description |
---|---|
Unconfigured | A direction integration that does not support boarding. This merchant connection is missing valid credentials |
Requirements | A platform connection that supports onboarding. One or more merchant data requirements is missing in order to onboard. |
Ready | A platform connection that has all merchant data requirements met to onboard. Onboarding has not occurred, but can be started. |
Queued | The merchant connection onboarding has been initiated in Preczn and is queued to be sent. This is relevant especially in scenarios where you may be bulk onboarding many merchants at the same time. |
Sent | Onboarding data has been sent to the connection and Preczn is awaiting a response to confirm onboarding/underwriting has started. |
Error | Error indicates that an issue has occurred while onboarding and in most circumstances includes a more detailed 'actionDescription' about the error itself. If an error occurs, please contact Preczn support and they will help resolved the issue. |
Underwriting | Onboarding data has been sent and the connection acknowledges that underwriting / review is in progress. |
Pending | (Deprecated - replaced with Underwriting ) |
RFI | The connection has started underwriting, but a 'Request For Information' has been returned for additional information. This will often accompanied with an 'Action Required' flag and Action Required Description. |
Active | Connection has valid account and credentials with the connection. This is the ideal end state for onboarding as it allows merchant to be assigned to a plan in order to perform Transactions with the connection. This state may also be achieved by directly entering Connection Credentials. |
Disabled | Connection has disabled the account due to missing data or other resolvable issues. |
Rejected | The connection has permanently rejected the merchants application and will not proceed with underwriting. |
Closed | The account at the connection is permanently closed. |
Cancelled | Merchant has cancelled or removed their underwriting application. |
Updated 5 months ago