Sending Payments

Submit an RTGS credit transfer as a signed ISO 20022 pain.001 document; the API responds synchronously with a pain.002 status document.

Endpoint

POST /pain.001/create/rtgs
Content-Type: application/xml
Accept: application/xml

Authenticated via your mTLS client certificate (see Authentication) — no separate token is needed on this call.

Request body

The XML body must contain both of the following elements, wrapped together (as is standard for ISO 20022 messages exchanged with a Business Application Header):

<AppHdr> — a Business Application Header (head.001.001.02)
<Document> — the pain.001.001.09 Customer Credit Transfer Initiation

The entire document must be XML-signed, and the signature must be verifiable against a document-signing certificate that was issued to your client application during enrollment. Unsigned or incorrectly signed requests are rejected before the payment content is even parsed.

Response

On success, the API returns a pain.002 (Customer Payment Status Report) as XML in the response body, describing the transfer's initial status.

Error handling

Status	Meaning
`401 Unauthorized`	XML signature is missing or does not verify against your on-file signing certificate(s).
`400 Bad Request`	Document doesn't contain a parseable `AppHdr` and/or `Document` element in the expected namespaces.
`500 Internal Server Error`	Unexpected server-side failure. Response body is a small `<Error><Message>...</Message></Error>` XML document, not a stack trace.

XML schemas (XSD)

Build the pain.001 message, its bcon business message envelope and the XML signature according to the Georgian ISO 20022 schemas published at altasoft.github.io/geo-iso20022. The site lets you browse each XSD and check a sample document against it with its XML Validator.

Message	Namespace	Used for
`bcon.001.001.01`	`urn:ge:bankconnect:xsd:bcon.001.001.01`	Signed `BusinessMessage` envelope for the request you send
`head.001.001.02`	`urn:iso:std:iso:20022:tech:xsd:head.001.001.02`	`<AppHdr>` Business Application Header
`pain.001.001.09`	`urn:iso:std:iso:20022:tech:xsd:pain.001.001.09`	`<Document>` Customer Credit Transfer Initiation
`bcon.002.001.01`	`urn:ge:bankconnect:xsd:bcon.002.001.01`	Signed `BusinessMessage` envelope for the response the bank returns
`pain.002.001.10`	`urn:iso:std:iso:20022:tech:xsd:pain.002.001.10`	Customer Payment Status Report in the response

The XSD files for all of these messages can be downloaded from github.com/altasoft/geo-iso20022/tree/main/xsds, one folder per message.

See the API Explorer for complete request and response examples.

Gap: This guide only covers the RTGS credit-transfer endpoint. If other payment rails or message types (e.g. non-RTGS transfers) are planned, confirm availability and endpoint paths with the bank — they weren't present in the reviewed API surface.