Skip to main content

Financial Operations

Below section describes error response codes from Client-API for finance operations.

  1. Error Response: POST/v1/{clientId}/create_account_mandates
HTTP Status CodeMeaningResolution TipError Response
400 Bad RequestMissing values in JSON payload-Check conditional mandatory fields are part of payload -Mandatory values are 1. mandateId 2. accountReference 3. providerName 4. debtorReference 5. productReferences{"messages":["body/['<entityId>'] should have required property '<field>'"],"messageIds":[],"success":false}
400 Bad RequestInvalid partial value set-Check one set of group fields are part of payload 1. providerName → ferratumCheckoutCreditCardV2 2. providerName → trustly 3. providerName → paylandsenBizum/paylandsenCards + clientIPAddress 4. providerName → split
200 OK Transaction status: failedInvalid ID-Entity is wrong. Check the field mentioned for duplicate resource created 1. accountReference 2. debtorReference{"ENTITYID":{"success":false,"messageIds":[],"messages":["Error processing message ""]}}
  1. Error Response: POST/v1/{clientId}/delete_account_mandates
HTTP Status CodeMeaningResolution TipError Response
400 Bad RequestMissing values in JSON payload-Check mandatory fields are part of payload -Mandatory values are 1. mandateId 2. accountReference{"messages":["body/['<entityId>'] should have required property '<field>'"],"messageIds":[],"success":false}
200 OK Transaction status: failedInvalid ID/s-Entity is wrong. Check the field mentioned for duplicate resource created 1. accountReference 2. mandateId{"ENTITYID":{"success":false,"messageIds":[],"messages":["Error processing message":]}}
  1. Error Response: POST/v1/{clientId}/create_promises_to_pay
HTTP Status CodeMeaningResolution TipError Response
400 Bad RequestMissing values in JSON payload-Check conditional mandatory fields are part of payload -Mandatory values are 1. amount 2. claimReference 3. currency 4. dueDate{"messages":["body/['<entityId>'] should have required property '<field>'"],"messageIds":[],"success":false}
200 OK Transaction status: failedInvalid ID/s-Entity is wrong. Check the field mentioned for duplicate resource created 1. claimReference{"ENTITYID":{"success":false,"messageIds":[],"messages":["Error processing message":]}}