# Contract Status GET /partner/v3/shops/:shopUuid/contracts/:contractUuid 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/v3/shops/:shopUuid/contracts/:contractUuid 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. For the flow which is to include down payment transfer, the contract status needs to be checked twice as well: - Firstly, after contract signing, the partner checks that the status of the contract is signed to see if the signing process has been completed. - Secondly, after the POST /payment-link API call, the partner checks the status of the contract to make sure the down payment transfer has been successful. If the status is activated, the purchase has been successfully financed by Inbank and the purchase items can be forwarded to the customer. 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. - In case of the redirect, send_to_signing_sms and send_to_signing_email signing methods, there is no certain time when the customer will perform the signing. In this case, the endpoint needs to be polled at a reasonable interval for 7 days. This is also applicable if the flow includes the income proof verification process. For detailed information on the income proof flow, please contact your Inbank representative. Endpoint: GET /partner/v3/shops/{shopUuid}/contracts/{contractUuid} Security: bearerAuth ## Path parameters: - `shopUuid` (string, required) The unique identifier of the shop. Example: "a93f1f44-d5dd-4469-bfcc-c1de9e969213" - `contractUuid` (string, required) The unique identifier of the contract. Example: "788ec8c4-c497-470b-8505-2303f151d427" ## Response 200 fields (application/json): - `contract` (object) Returns contract details. - `contract.status` (string) Contract status. Example: "unsigned" - `contract.terminationReason` (string) Contract termination reason type. - `contract.uuid` (string) Contract UUID. Example: "11d1baeb-1da1-1c01-b111-12111211c1a1" - `contract.number` (string) Contract number. Example: 89001350000 - `contract.payoutAccountNumber` (string) Payout account number. Example: "EE19824845453792774580000000" - `contract.activatedAt` (string) Activated at. - `contract.activatorName` (string) Contract activator name. - `contract.terminatedAt` (string) Contract terminated at. - `contract.productCode` (string) Product code. Example: "insurance_fin" - `contract.customerSigned` (string) Customer signed at. - `contract.repSigned` (string) Rep signed at. - `contract.signedAt` (string) Signed at. - `contract.partnerApprovalAt` (string) Partner approval at. - `contract.customerUuid` (string) Contract customer UUID. Example: "40837f6d-0000-0000-0000-59a5b1efedd8" - `contract.identificationSatisfied` (boolean) Customer identification acceptance status for contract. Example: true ## Response 401 fields (application/json): - `message` (string) Unauthorized Example: "unauthorized" ## Response 403 fields (application/json): - `message` (string) Unauthorized access Example: "User is not authorized to access this resource with an explicit deny" ## Response 404 fields (application/json): - `message` (string) Not found ## Response 500 fields (application/json): - `message` (string) Internal server error Example: "internal_server_error"