# Credit Applications Credit applications are the initial step in the Inbank financing process. Once the application is reviewed and accepted by the customer, a credit contract is created. ## Credit Application Submission - [POST /partner/v2/shops/{shop_uuid}/applications](https://docs.inbank.eu/api/direct-api-pl-flow-archived/credit-applications/postapplications.md): Credit applications are the initial step in the Inbank financing process. Once the application is reviewed and accepted by the customer, a credit contract is created. POST /partner/v2/shops/:shop_uuid/applications A credit application is submitted using the POST /partner/v2/:shop_uuid/applications endpoint. The credit application contains the credit period and amount, identification data and other information regarding the customer and the purchase. Once the e-shop receives a response to the payment session initiation request with the redirect URL and the UUID of the session, it can forward the data of the credit application to Inbank. To submit credit application data to Inbank, use the POST /partner/v2/shops/:shop_uuid/applications request. Request payload consists of several sub-objects: - credit_application: monthly income, product code and other credit related data - customer: customer\'s identity code, name and gender - customer_contact: customer\'s email and phone number - customer_addresses: customer's address details - customer_identification: the type of customer identification document and its number - consents: customer's consent for processing of their data - purchase: details about the purchased items - partner_urls: URL for the callbacks about the process status updates. The table below lists all parameters from the objects within the payload. Parameters can either be required or optional, depending on the integration flow. Please, consult your Inbank contact about your specific case. The decision_status parameter can have the following values: positive, negative, manual_negative, failed, income_proof_required, pending, manual. It can be considered that the application received a positive decision if its decision_status is positive. Usually, a new application has decision_status as pending until the decision is reached. Important note for test environments Document number, phone number and email of one customer cannot be used for another customer. For testing purposes it means that if you introduce a new identity code, you should also generate a new document number, phone number and email address. If you use an existing customer's identity code, you can use both existing and new values for document number, phone number and email address. Due to banking secrecy we cannot indicate the exact reason behind the application failure (e.g. customer with such an email already exists) and will return a generic error: "Error has occurred, contact customer support". ## Create Signing for Application - [POST /partner/v2/shops/{shop_uuid}/applications/{application_uuid}/signings](https://docs.inbank.eu/api/direct-api-pl-flow-archived/credit-applications/postsignings.md): POST /partner/v2/shops/:shop_uuid/applications/:application_uuid/signings After the customer has reviewed the application, they can proceed to application signing which is done via the POST /partner/v2/shops/:shop_uuid/applications/:application_uuid/signings endpoint. There are the following signing methods available: - digital - the method is used in cases when the partner has a separate signing solution. The request with the digital signing method is used as a confirmation that signing has been successful. - paper - the method is used if you are collecting paper applications signed by the customer. - sms - with this method the signing is done using an SMS code. After you send the request, the customer will receive an SMS with the code from Inbank. After that, the code is sent over to Inbank for confirmation via the PATCH /contracts/:contract_uuid/signings request. ## Update Signing for Application - [PATCH /partner/v2/shops/{shop_uuid}/applications/{application_uuid}/signings](https://docs.inbank.eu/api/direct-api-pl-flow-archived/credit-applications/patchsignings.md): PATCH /partner/v2/shops/:shop_uuid/applications/:application_uuid/signings To confirm the signing the customer needs to enter the code they received to their mobile from Inbank. The code is sent over to Inbank for confirmation via the PATCH /partner/v2/shops/:shop_uuid/applications/:application_uuid/signings endpoint. ## Application Details - [GET /partner/v2/shops/{shop_uuid}/applications/{application_uuid}](https://docs.inbank.eu/api/direct-api-pl-flow-archived/credit-applications/getapplication.md): To check whether a credit application received a decision from Inbank and display the credit offer, the partner needs to get the data of the application and credit details using the GET /partner/v2/shops/:shop_uuid/applications/:application_uuid request. As the decision process might take some time, the endpoint may need to be polled once a second for a maximum of 30 seconds. The response includes the decision_status parameter which can have one of the following values: pending, positive, manual_negative, income_proof_required, negative, failed. It can be considered that the application received a positive decision from Inbank if its decision_status is positive. Once the partner receives a positive credit decision from Inbank, it can display the offer to the customer. If the response includes the income_proof_required decision status, the customer needs to submit their income proof documents to Inbank. Note that there are situations when the application data may be altered by Inbank systems during processing, in that case the application is also assigned a new UUID and the returned application data contains the attribute changed_conditions with value true. The changed_conditions attribute informs you if the application has undergone changes or not. If you persist Inbank application UUID in your system - you should always compare the returned UUID with the one you requested and update the UUID on your side respectively. ## AIS Bank List Retrieval - [GET /partner/v2/shops/{shop_uuid}/account_statements/bank_list/{application_uuid}](https://docs.inbank.eu/api/direct-api-pl-flow-archived/credit-applications/getbanklist.md): GET /partner/v2/shops/:shop_uuid/account_statements/bank_list?application_uuid=application_uuid The AIS endpoints are used to submit the income proof statement or for AIS verification of the customer. In cases when the application receives the income_proof_required decision, the flow needs to include the AIS upload process. The first step is retrieving the list of available banks from which the account statement can be provided via the GET /partner/v2/shops/:shop_uuid/account_statements/bank_list API request. The request returns the name, ID and icon URL for each of the available banks. The selection of the banks needs to be displayed to the customer. Please note that the selection of banks is subject to change. In cases when the customer needs to go through AIS verification these endpoints need to be used after contract signing. You can find the details of the flows here. ## AIS Upload Session Initiation - [POST /partner/v2/shops/{shop_uuid}/account_statements/initiate_retrieval](https://docs.inbank.eu/api/direct-api-pl-flow-archived/credit-applications/postsessioninitiation.md): POST /partner/v2/shops/:shop_uuid/account_statements/initiate_retrieval Once the customer selects a bank, the AIS upload session can be started using the POST /api/partner/v2/shops/:shop_uuid/account_statements/initiate_retrieval API request. The response includes the redirect URL to which the customer should be forwarded to complete the AIS upload process. Once that process is complete, the customer will be redirected back to your site, to the return URL you have indicated in the request body. To learn the new decision which the application has received after the AIS upload and processing, the GET /partner/v2/shops/:shop_uuid/applications/:application_uuid endpoint needs to be polled until there is a new decision_status. The usual processing time is within 1 working day. ## Attach Files to Credit Application - [POST /partner/v2/shops/{shop_uuid}/applications/{application_uuid}/attachments](https://docs.inbank.eu/api/direct-api-pl-flow-archived/credit-applications/postattachments.md): POST /partner/v2/shops/:shop_uuid/applications/:application_uuid/attachments The account statement file can be forwarded to Inbank via the POST /partner/v2/shops/:shop_uuid/applications/:application_uuid/attachments endpoint. If applied, this endpoint needs to be used instead of the AIS upload related endpoints. Please note, as income proof documents are processed by Inbank representatives in case of a manual upload, income verification can take some time. To learn the new decision the application has received after the account statement upload and processing, the GET /partner/v2/shops/:shop_uuid/applications/:application_uuid endpoint needs to be polled until there is a new decision_status. Request body parameters: Attachments must be submitted as form-data. cURL example: --form "attachments[]=@/path_to/file1.pdf" --form "attachments[]=@/path_to/file2.pdf" ## Application Approval - [POST /partner/v2/shops/{shop_uuid}/applications/{application_uuid}/accept](https://docs.inbank.eu/api/direct-api-pl-flow-archived/credit-applications/postapplicationaccept.md): POST /partner/v2/shops/:shop_uuid/applications/:application_uuid/accept After the credit application receives a positive decision and the credit offer is presented to the customer, they can choose to accept the offer, which is done through the POST /partner/v2/shops/:shop_uuid/applications/:application_uuid/accept endpoint. Accepting the application automatically creates a contract and returns the identifier of the contract in the response. ## Application Cancellation - [POST /partner/v2/shops/{shop_uuid}/applications/{application_uuid}/cancel](https://docs.inbank.eu/api/direct-api-pl-flow-archived/credit-applications/postapplicationcancel.md): POST /partner/v2/shops/:shop_uuid/applications/:application_uuid/cancel After the credit application receives a positive decision and the credit offer is presented to the customer, they can choose to cancel their credit application, which is done through the POST /partner/v2/shops/:shop_uuid/applications/:application_uuid/cancel endpoint.