# Credit Contracts Credit contracts contain the details of the financing agreement between the customer and Inbank. Once the contract is activated, the partner is to supply goods/services to the customer. ## Contract Printout - [GET /partner/v2/shops/{shop_uuid}/contracts/{contract_uuid}/printouts](https://docs.inbank.eu/api/direct-api-pl-flow-archived/credit-contracts/getprintouts.md): GET /partner/v2/shops/:shop_uuid/contracts/:contract_uuid/printouts The details of the contract are included in the printout which can be retrieved using the GET /partner/v2/shops/:shop_uuid/contracts/:contract_uuid/printouts endpoint. The response includes the link to the contract printout file. ## Create Signing for Contract - [POST /partner/v2/shops/{shop_uuid}/contracts/{contract_uuid}/signings](https://docs.inbank.eu/api/direct-api-pl-flow-archived/credit-contracts/postcontractssignings.md): POST /partner/v2/shops/:shop_uuid/contracts/:contract_uuid/signings After the customer accepts the credit offer and has reviewed the contract, they can proceed to contract signing which is done via the POST /partner/v2/shops/:shop_uuid/contracts/:contract_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 contracts 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 Contract - [PATCH /partner/v2/shops/{shop_uuid}/contracts/{contract_uuid}/signings](https://docs.inbank.eu/api/direct-api-pl-flow-archived/credit-contracts/patchcontractssignings.md): PATCH /partner/v2/shops/:shop_uuid/contracts/:contract_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/contracts/:contract_uuid/signings endpoint. ## Contract Status - [GET /partner/v2/shops/{shop_uuid}/contracts/{contract_uuid}](https://docs.inbank.eu/api/direct-api-pl-flow-archived/credit-contracts/getcontractuuid.md): GET /partner/v2/shops/:shop_uuid/contracts/:contract_uuid Once the credit contract UUID has been retrieved and the contract has been signed, the partner can check the status of the credit contract using the GET /partner/v2/shops/:shop_uuid/contracts/:contract_uuid request. The response will include the status parameter. If the status is activated, the purchase has been successfully financed by Inbank and the purchase items can be forwarded to the customer. If the flow includes merchant approval, the merchant checks if the status of the contract is signed. When the contract is in the signed status, the merchant needs to approve or cancel the contract. If the merchant approved the contract, they need to check if the contract status has been changed to activated, which indicates that the purchase was successfully financed by Inbank. As customer signing processing might take some time, the endpoint may need to be polled for a certain amount of time. In case of digital, sms or paper signing methods, the endpoint needs to be polled once every second for a maximum of 15 seconds. The response may include the process_status parameter, which you might need to take into account for certain flows. The flows are described here. The related process_status values are: - waiting_for_customer_digital_verification - the customer needs to go through AIS verification. - waiting_for_partners_confirmation - the contract is waiting for partner approval. ## Contract Merchant Approval - [POST /partner/v2/shops/{shop_uuid}/contracts/{contract_uuid}/merchant_approval](https://docs.inbank.eu/api/direct-api-pl-flow-archived/credit-contracts/postmerchantapproval.md): POST /partner/v2/shops/:shop_uuid/contracts/:contract_uuid/merchant_approval Give merchant approval for contract activation. This endpoint can be used only in case it's agreed with Inbank. If used, then contract will not be activated before merchant's approval is given. This endpoint is relevant, for example, when there is a need to double-check that the required goods are available. If the flow includes merchant approval, the merchant checks if the status of the contract is signed using the GET /partner/v2/shops/:shop_uuid/contracts/:contract_uuid request. When the contract is in the signed status, the merchant needs to approve or cancel the contract. To approve the contract, the e-shop needs to know the credit contract UUID, which is in the response to the POST/:application_uuid/accept request. The request does not require any parameters to be passed in its body. Note that you can also approve contracts in the Partner Portal. ## Contract Cancellation - [POST /partner/v2/shops/{shop_uuid}/contracts/{contract_uuid}/cancel](https://docs.inbank.eu/api/direct-api-pl-flow-archived/credit-contracts/cancelcontract.md): POST /partner/v2/shops/:shop_uuid/contracts/:contract_uuid/cancel If the flow includes merchant approval, the merchant checks if the status of the contract is signed using the GET /partner/v2/shops/:shop_uuid/contracts/:contract_uuid request. When the contract is in the signed status, the merchant needs to approve or cancel the contract. To cancel the contract, the e-shop needs to know the credit contract UUID, which is in the response to the POST/:application_uuid/accept request. The request does not require any parameters to be passed in its body. Note that you can also cancel contracts in the Partner Portal.