Definition

User represents the business you want to pay. It's the equivalent of a seller, the beneficiary of a payment. You need to create a User before requesting a Loan. Users don't have an Aria account: it's your responsibility to create and update them.

According to use cases, a User can be :

• A freelancer
• A supplier
• A seller

A User will always be the business company that benefits from an invoice payment.

Terms of Service

Your Users (beneficiaries) must accept our Terms of Service when they are the invoice owner before a Loan is created. You have two options:

1. Use our User Contract feature to send the Terms of Service directly to the User for their signature.
2. Obtain the User’s consent to our Terms of Service on your platform, then create a tosAcceptance using our API (or the upcoming dashboard version). Use this URL {url} to display the Terms of Service to your Users, as each consent will be dated and stored. This ensures we can track the exact version of the Terms that each User agreed to.

In some cases, we may require you to use the first method.

Please note: Creating a loan for an invoice-owning User without this consent will result in a loan refusal.

User Contract

The User Contract is the first method described above: Aria sends its Terms of Service to the User for electronic signature. You trigger it through the API, and the current state is always exposed on the User's contractStatus field.

Contract statuses

contractStatus tells you where the User stands in the signature flow:

• notSent: no contract has been sent to the User yet.
• pending: the contract has been sent and is waiting for the User's signature.
• completed: the User has signed and the contract is fully executed.
• voided: the contract was cancelled and is no longer valid. A new one has to be sent.

Sending a contract

Use Send user contract (POST /companies/{companyId}/user/USERID/contract) to create a contract and send it to the User for signature. The User receives an email with the signature request, and contractStatus moves to pending.

Send it when the User has no contract yet, or when the previous one is voided or was never sent. In each of these cases a fresh contract is created.

Resending a contract

If the User did not receive or lost the original email, use Resend user contract (POST /companies/{companyId}/user/USERID/contract/resend) to send the signature request again. This resends the exact same contract, so no new contract is created.

📘

Resend only works while the contract is pending. A completed contract cannot be resent, and a voided or never-sent contract has to go through Send user contract, which issues a new one.

Identity check

KYC procedures have been set up to manage AML/CFT risks since Aria provides financing.

Before paying a user, you have to provide information that you can find in our API Reference. All information is mandatory to fully identify the beneficiary.

We may require proof of identity from the company's legal representative.

KYC docs verification is performed within a 24-hour time frame, from Monday to Friday (Paris Time Zone).

We provide 3 statuses:

• PENDING: The KYC doc is not yet verified.
• VALID: The KYC doc is valid.
• INVALID: The KYC doc is invalid.

📘

We will help you set up your KYC process during your onboarding phase.