Credit transfer instruction endpoint.Copy Pagepost https://www.bankingcircleconnect.com/api/v1/payments/credit-transfer-instructionsCredit transfer instruction endpoint.HeadersContent-TypestringMediatype of input resource.Supported Values:- "multipart/form-data; boundary=[string]" (Boundary is a delimiter of data parts in the input.)AcceptstringrequiredThe Accept header is used to inform the server which content type is understandable by the client expressed as MIME-types.Supported Values:- */* (derived from Content-Type)- application/xml; profile="urn:iso:std:iso:20022:tech:xsd:pain.002.001.10" (Supported only for Content-Type "multipart/form-data" with a file in pain.001.001.09 format)Idempotency-KeystringUnique value generated by the user which the API uses to recognize subsequent retries of the same request.This field is limited to a maximum of 100 characters, if not upheld the API will return with an error 400 - Bad Request.Example: 2b7b05ad-4411-4a19-8c95-2508b17e0fd8TruncatestringFor internal reasons we have some fields with stricter length requirements compared to the ISO standard. You can "instruct" us to do truncation for these particular fields by setting this header to "true". It is however recommended that the caller performs truncation on their side to prevent unexpected data loss. The Truncate header is there for callers who for any reason are not able to do so.Responses 201Success: All payments accepted 400Bad request: Request is not correctly formulated (malformed XML, invalid idempotency key). Returns JSON error envelope. 406Not Acceptable: The Accept header does not include a supported response format for this request type. Returns JSON error envelope. 409Conflict: Idempotency-key violation. Returns JSON error envelope. 415Unsupported Media Type: Content-Type is not supported. 422Unprocessable Entity: Request was parsed but payments were rejected. 500Internal Server Error: An unexpected fault occurred.Updated 43 minutes ago