Jaris
Jaris is a service provider for B2B loans.
Jaris is a service provider for B2B loans. Through Preczn’s integration with Jaris, platforms can send anonymized merchant data to Jaris to assess loan eligibility.
Once a merchant qualifies, platforms can use the embeddable Preczn JavaScript component to enable merchants to apply for loans and securely transmit their data to Jaris at the time of application.
Preczn monitors the loan process and shares real-time status updates as they are received from Jaris.
Overview
Below is a summary of the connection key facts to support your integration.
Category | |
---|---|
Processor Type | Loan Service Provider |
Preczn Enumeration | Jaris |
Documentation | Jaris Developer Docs (Please contact Jaris for access) |
Supported Features
The following features are supported for this connection:
Merchant Onboarding
Features | Supported |
---|---|
Merchant Onboarding | ✅ Yes |
Loan Origination
Features | Supported |
---|---|
B2B Loan Origination | ✅ Yes |
B2B Loan Monitoring | ✅ Yes |
Managing Merchant Eligibility and Sending Anonymized Data
Preczn has integrated with Jaris to share merchant data and anonymized tr in order to determine merchant eligibility for Jaris loans.
The Preczn/Jaris workflow is very similar to boarding a merchant. From a high level perspective, the merchant status flow operates in the following manner:
Requirements
- The merchant is missing subset of the data needed for Jaris to start reviewing if the merchant is eligible for a loanReady
- The merchant has the minimal amount of data to board to JarisPartialBoarded
- The merchant data has been sent to Jaris and additional anonymous transactions are being sent. Loan offers may be issued and available to the merchant at this point.Active
- The merchant has opted into an offer and Preczn has sent the full merchant data record to Jaris.
Required Merchant Data
Jaris evaluates if a merchant is available for a loan offer by evaluating subset of their merchant data (like how long they've been in business) and their on going transactions. This let's Jaris build a profile of the merchants credit worthiness and the value of a loan that can be offered.
Jaris requires a minimal amount of merchant data in order to start evaluating if the merchant is eligible for a loan. Note that the full merchant data set is only sent to Jaris once a merchant opts into a loan offer.
A merchant must have a minimum of the following data:
Required Field to Board |
---|
address.region |
dateEstablished |
mcc |
name |
owner.firstName |
Starting Boarding
Once a merchant has the required data, the merchant's Jaris status will change to Ready
. At this point, the merchant can be boarded to Jaris in order to start evaluating if they are eligible for a loan.
To start this process, use the Onboard Merchant to Connection endpoint, specifying Jaris
as the connection.
Doing so will queue the merchant to be boarded to Jaris, setting the status to Sent
.
When the merchants data and historic transactions have been sent to Jaris, the merchants status will change to PartialBoarded
. At this point you will want to monitor is Loan Offers are sent for the merchant.
Tracking and Displaying Loans to Merchants
About Jaris Loans
Once a merchant has been PartialBoarded
to Jaris, Jaris will begin to evaluate and extend loan offers to the merchant.
These loans are created and tracked inside Preczn as B2B
loan objects. We'll cover how to retrieve the loans and listen for loans in the following sections:
Each of the B2B
Jaris loans will have a corresponding status Merchants are eligible to originate a loan as soon as a loan is created with a Preoffer Created
status:
Status | Notes |
---|---|
Preoffer Created | Original Status of the Jaris loan. Indicates that a merchant is eligible for a loan and can have the Jaris Client Component displayed. |
Preoffer Accepted | |
A application has been fully submitted | |
A final approval has occurred | |
A final acceptance must be done by the merchant | |
A loan exists and is awaiting funding | |
A created loan has been approved and funds sent to the merchant bank account | |
An active loan has been closed and is considered no longer active | |
An active loan is in danger of defaulting | |
An active loan has defaulted | |
A loan was canceled by either party before funding |
Listening for Loan Offers
Preczn offers loan webhook events in order to communicate when loans are created and updated.
To listen for loan events, you can create a new Preczn webhook or modify existing Preczn webhooks to listen for the following events:
- loans.created
- loans.updated
When a loan is created for a merchant, this is an indication that the Jaris Client Component can be displayed in your application in order for the Merchant to review the preoffer, accept the loan, and fill out the Jaris application. You can read more about this in the Displaying Loans to Merchants section.
Retrieving Loans
If at any point in time you with to retrieve a loan or series of loans for a merchant, you can use the Preczn Loans Endpoints:
- Get Loans
- The Get Loans endpoint allows you to return all loans for your platform. If desired, results can be narrowed to specific merchants. If you have various loan types (B2B2B or B2B) you may also narrow down the results based on type
- Get Loan
- Each Preczn loan has a unique ID. The Get Loan endpoint allows you to retrieve the latest loans data from the preczn database.
Displaying Loans to Merchants
When a loan preoffer has been created for a merchant, you will want display the Jaris Connect interface for your merchant to review and accept the offer.
Jaris offers an embeddable component to handle the display of the available offers for a given merchant. To simplify implementation of a Jaris B2B Lending on Preczn, you can embed the Jaris Connect interface on your web interface using a secure, Preczn-hosted JavaScript client.
1. Include the Preczn jaris client on your page
Add the secure, hosted JavaScript reference in the <head>
of your page:
<script src="https://api.preczn.com/v1/clients/jaris.min.js?merchantId={{merchantID}}&publicApiKey={{PrecznAPIKey}}"></script>
2. Define the jaris Connect location
Define the location for the button on your page, we suggest containing it within a <div>
:
<div id="jaris-container" style="width: 800px"></div>
3. Define the required JavaScript callback function
Define a JavaScript callback function to handle errors:
var jarisCallback = function(errors) {
console.error(`jaris errors:\r\n - ${errors.join('\r\n - ')}`);
}
If an errors occurred, the errors
parameter value will contain an array of strings describing any error conditions.
4. Render the offer
Call the Preczn JavaScript client to create the button:
<script type="text/javascript">
Preczn.jaris.renderOffer("jaris-container", jarisCallback);
</script>
The renderOffer
function takes 2 parameters, in this order:
Parameter | type | Description |
---|---|---|
Container ID * | string | The HTML DOM element ID for the element which will contain the jaris Connect offer interface (we suggest containing it within a <div> element) |
Callback Function * | function | The function to call when jaris Connect returns an error. |
* Denotes a required parameter.
This will load all of the required scripts and stylesheets from both Preczn and jaris into the <head>
of your page, and render the jaris Connect offer!

Error conditions
If any error conditions occur - such as invalid merchantId
, failed authentication, etc. - then the Preczn jaris script will not load any dependencies or render the jaris Connect offer on your page.
Instead, the error callback function will be called with an array of error strings.
Error | Description |
---|---|
Invalid API Key. | The provided publicApiKey was not valid. |
Merchant not found. | The provided merchantId was not a valid merchant ID. |
Invalid Jaris token or shopId. | The jaris connection has an invalid configuration. |
Using with a Content Security Policy
If you are using a Content Security Policy to secure your client-side web application, you will need to extend your policy to allow jaris.min.js to load and connect to the Preczn API, as well as to load the jaris scripts and connect to jaris.
Please add the following directives to your content security policy:
Directive | Values |
---|---|
script-src | api.preczn.com *.jaris.com *.jaris.co |
connect-src | api.preczn.com *.jaris.com *.jaris.co |
Data Transfer After User Accepts Preoffer
When a merchant accepts the preoffer by clicking "Apply Now", they are opting into the Jaris Terms of Service. At this point, Preczn will transmit the merchants full data set of business information, owners, and banking details to Jaris.
At this point, the merchant will continue through the Jaris component to complete their application, where the available data will already be pre-populated. Merchants have the option to review and update their data at this time.
Data Transfer Wait - In Progress
During the data transfer, it is possible that the Jaris application renders before all merchant data can be transmitted. Preczn is working with Jaris to determine a solution for the application to wait until all data is transferred before the application renders, thus ensuring that all data is prefilled.
Updated 10 days ago