FAQ

Which ISO 20022 messages are supported?

Depending on the API, the platform supports:

• pacs.008 – Customer Credit Transfers
• pacs.009 – FI Credit Transfers
• pacs.004 – Returns
• camt.056 / camt.029 – Cancellation and return-related flows
• camt.110 / camt.111 – Investigations
• pain.013 / pain.014 – Drawdowns

Additional message types may be introduced as the platform evolves.

What is the difference between v2 and v3 APIs?

Some v2 endpoints are deprecated and maintained only for backward compatibility. v3 APIs are the current, supported contracts and should be used for all new integrations.

What is InstitutionUniversalId and why is it required?

InstitutionUniversalId uniquely identifies an Institution, Environment, and Brand combination. It is required on every API call to ensure correct routing, configuration, entitlements, and processing behavior.

How are user permissions enforced?

User permissions are exposed through Abilities APIs for Enterprise users. These APIs return fine-grained capabilities such as:

• Viewing wires
• Creating wires
• Approving or rejecting as debtor or creditor
• Managing drafts
• Controlling fees
• Managing OFAC and notifications

Client applications should use these permissions to drive UI behavior and authorization decisions.

How do I create a customer wire?

Customer wires are created using the v3 Customer Credit Transfer API, which accepts a structured JSON payload aligned with the pacs.008 ISO message. Required data includes amount, debtor, creditor, and remittance information.

Do I need to provide a UETR?

No. If a UETR is not provided, the system automatically generates one.
For drawdown-related flows, the provided UETR must match the original drawdown request already stored in the system.

Can I edit a wire after it is created?

Once a wire is submitted and enters processing, the wire cannot be edited. If the money has not yet moved in the core, the wire can be rejected and used to prepopulate a new one using “Reject and copy to new”.

What validation is performed on wire creation?

The APIs enforce strict validation, including:

• Amount format and limits
• Account ID patterns and length
• ISO country code validation
• Required fields based on ISO message rules

Invalid requests return validation errors.

What are draft wires?

Draft wires allow users to save incomplete wire information and complete or submit it later. Draft-related capabilities are controlled via user abilities.

What are wire templates?

When an incomplete wire, or just a wire that is not meant to be submitted, is saved for later, it can be saved as draft or as a template. A template is nothing but a draft with a template description and so the same draft endpoints will be used to retrieve and manage templates.

How are returns handled?

Returns are processed through dedicated APIs aligned with pacs.004 and camt message standards. Returns preserve the original transaction context and audit trail instead of modifying the original wire.