The XML Input files you send to Cross River (CR) for processing must include certain building blocks. These building blocks are part of the ISO 20022 standard. The following topics describe the generic building blocks and elements that CR needs you to include so we can process your files.

The first page under this topic describes the Input 

  , which is used for Book (internal) transfers, ACH Push transfers, and Fedwire transfers. The second page describes the 

 , which is used for Direct Debit transfers.

You can include up to 250,000 transactions in each file you send through Unicorn.

Sending and receiving files

Preparing Your Input XML File

var_miha

new_var_2

new_mih_var

mih_var

This is a plain text that will be inserted in an expandable heading for using this raw as an exampl

testheight

available

testulet

testvar

altscenario

This is a plain text that will be inserted in an expandable heading for using this raw as an example

scenario

exemplu

variabila

Archbee

text

PAIN.001.001.03 input file

Bank rails

Payment options

Use cases

Workflow

Rail types

PAIN.008.001.02 input file

Requirements for XML Files per Rail

Book Transfer

ACH CCD/PPD

Fedwire

Direct Debit

XML Input File Examples

Output Files

Validation

Status and error codes

ISO20022 payments

Payment process flows

Originate a payment

Simulate inbound payments

Originate a client batch

Working with ACH

RTP via TCH payment process flows

Query the directory

Instant Payment queuing

Instant Payment limits

Instant Payments

International Payments process flow

Send an international payment

International Payments in Explorer

International Payments

Simulate an inbound payment

Originate a drawdown request

Respond to a drawdown request

Authorization

Holds

Payment Templates

Working with Wires

Wires

Use Cases

Cancel a payment

INTERNAL-Working with XPay

Working with XPay

XPay