This section describes the XML file requirements for the following payment methods (rails):

For more information on the code structure for each payment method, see the corresponding topic in the XML Input File Examples section.

See Preparing Your Input XML File for more details on the blocks and tags used in the XML examples below.

For book transfers (among 2 accounts within CR):

Both the DbtrAgt block and the CdtrAgt block must contain CR's routing number (021214891) in the MmbId element.

When sending funds from one of your COS Partner bank accounts to another of your COS Partner bank accounts, Unicorn will transfer the funds with an internal book transfer.

For ACH Push CCD transfers, the PmtTpInf block must be according to the following example:

All the above fields are required. Unicorn looks for these fields in order to know what type of transaction you are requesting. If it can’t find any of these, it will cause an error.

For ACH Push PPD transfers, the PmtTpInf block must be according to the following example:

All the above fields are required. Unicorn looks for these fields in order to know what type of transaction you are requesting. If it can’t find any of these, it will cause an error.

For Fedwire payments:

For ACH direct debits:

For example:

All the fields shown above for Direct Debit are required so that Unicorn can identify the payment type and details.

This is how you should structure your XML for sending funds using RTP.