ISO20022 payments

Workflow

2min

Prior to using Unicorn, as part of the onboarding process, the Unicorn support team will register your account numbers with the Unicorn system. These will be the account numbers that you will use to originate transactions via Unicorn. The rails that you use for payment processing will also be defined at this point.

Unicorn receives transaction requests in the form of XML files produced by your treasury management system (TMS), and initiates those transactions with COS (CR's banking core). Unicorn functions as the file translator to process your transactions. It initiates transactions, records them, listens for updates on the transactions and produces status reports which you can view.

Further reports are generated after every significant change in status relating to a transaction.

The Unicorn workflow is as follows:

  1. Prepare an XML file using your TMS
  2. Send Unicorn the XML file via Unicorn's SFTP server
  3. Unicorn polls the SFTP server every 30 minutes
  4. When Unicorn identifies an XML file, it parses it, and validates the file (validation)
  5. Transactions are initiated in the CRB banking core, based on the XML file
  6. The CRB banking core returns the results of the transaction process to Unicorn
  7. Unicorn outputs status files (PSRs) via SFTP, reporting on the latest status of each file, batch and transaction
Document image




🤔
Have a question?
Our super-smart AI, knowledgeable support team and an awesome community will get you an answer in a flash.
To ask a question or participate in discussions, you'll need to authenticate first.



Updated 07 Oct 2024
Doc contributor
Did this page help you?