Skip to content

The method of creating a client, application, contract, as well as DDS with the Issuance process based on the transmitted aggregated data

POST

This method creates in BI objects a client, an application, a contract, a schedule and a client account, which reflects the issuance of funds and adds new entries to the directory.

This method uses the LOAN_APPLICATION arrival channel. For this method to work correctly, the PRL scheme for the LOAN_APPLICATION arrival channel must be end-to-end. For example, one expression that will always be executed (2> 1). This is necessary so that when the application is saved and the lead is automatically created, this DSS is launched, executed successfully and affixed the status of the application “For issuance”. After the requisition accepts this status, a contract can be created. Now in the code, the method can wait for some time until the application accepts this status. But if gateway checks and / or manual verifications are performed on the DSS, then, accordingly, the automatic creation of a contract becomes impossible in its current form and, accordingly, an error will be returned that the status of the order is not the one it should be (WRONG_LOAN_APP_STATUS_FOR_CONTRACT_CREATION_ERROR).

Also, the "Automatic contract creation" checkbox should not be in the "Receipt channel", otherwise the "CHANNEL_SCHEMA_MUST_BE_WITHOUT_AUTO_CONTRACT_CREATION_ERROR" error will be returned.

You can find the setting of the PRS and the channel of receipt here at this link /documentation/article/270.

A description of the business rules for this method can be found at the link /documentation/article/265.

For a description of possible errors, see this link /documentation/article/266

Request Body

application/json
object
object

Borrower

Email Address

Client name ( borrower)

Client (Borrower) GUID

Client's last name ( borrower)

Mobile phone number

object

The identifier of the "Consultant" catalog item

Format"int64"

Consultant's full name

object

Contractor ID . If id is not specified, new elements of the directory are created with the name specified in the "name" parameter

Format"int64"
object
object[]

Tranches

object

Loan (contract)

Barcode (barcode)

Format"int64"

Interest rate on delay. If the delinquencyIntRate field is not specified for the fields of the loan object (or a null value is passed in it), then this field is filled with the value from the loan product

Format"double"
object[]

Additional service. If null is passed as this collection, then all fees will be taken from the credited product (if any)

Interest rate. If the interestRate field is not specified for the fields of the loan object (or a null value is passed in it), then this field is filled with the value from the loan product

Format"double"

Loan amount

Format"double"

Seller Commission

Format"double"

Loan (contract) GUID

The number of days between redemptions. If the trancheDuration field is not specified for the fields of the loan object (or null is passed in it), then this field is filled with the value from the loan product

Format"int32"

Number of tranches. If the tranchesQty field is not specified for the fields of the loan object (or null is passed in it), then this field is filled with the value from the loan product

Format"int32"
object

Vendors Guide

Identifier of the "Sellers" lookup element

Format"int64"

Seller

object

Directory "Stores" (Outlet)

Store ID . If id is not specified, new elements of the directory are created with the name specified in the "name" parameter

Format"int64"
object

Planned schedule

object[]

Tranches

Responses

OK

*/*
object

The identifier of the created item of the "Invoices" lookup

Format"int64"

If the element is successfully added to the directory, the status "ok" is returned. Otherwise, an error is returned

Valid values"error""ok"

Returns the date + time (kernel) in unix timestamp format in milliseconds

Format"int64"