XPay

Use XPay to transfer funds directly between 2 different partners inside the Cross River operating system (COS). Because you are transferring funds inside COS, the transfer happens immediately. Funds do not leave the bank with XPay transfers. A transfer can be a push or a pull.

Note

COS does not allow internal book transfers between 2 different partners to reduce the risk of transferring funds to the wrong party.

How XPay works

There are 2 payment flows in XPay:

Push
Pull

For both push and pull transactions, funds move between accounts under different partners, and are available immediately.

XPay configuration

For XPay transactions to complete, both the originating and receiving partners must have the appropriate pull or push functionality configured. By default, push functionality is turned on, with both Receive Push Enabled and Auto Approve Push set to Yes. Both Send Pull Enabled and Receive Pull Enabled are by default set to No for all accounts meaning that pull is turned off. Contact your Onboarding or Relationship Manager to enable pull functionality.

If the sending partner doesn’t have XPay enabled, the payment fails. The sending partner receives a synchronous error message.

If the receiving partner doesn’t have XPay enabled, the payment fails. The sending partner receives an asynchronous error message.

Push payments

Initiate. You initiate a payment to another CR partner. COS receives the request.
Route. COS routes the payment from your account to the receiving partner account.
Receive. The payment posts to the receiver account.
Settlement. Your account is debited.

Pull payments

Request. You request to pull funds from another CR partner. COS receives the request.
Approve. The partner receiving the pull request approves the request.
Route. COS routes the payment from the account of the partner receiving the pull request to your account.
Receive. The payment posts to your account.
Settlement. Your account is credited.

Approvals

Approval of push transactions is enabled by default as part of XPay configuration. When enabled, all inbound XPay push transactions approve and post automatically.

For pull transactions there is no Auto Approve Pull, so funds will not leave your account with no warning.

Participants

Sending partner. The partner sending the funds or originating a fund request via XPay. Also sometimes called the originating partner.
Receiving partner. The partner receiving the funds or fund request via XPay.
COS. The Cross River Operating System, CR’s core banking system, which performs the transfer between partners.

Business reference information

XPay

Transaction Types

Type	Description
Push	A credit payment being sent from an sender to a receiver
Pull	A debit payment being taken from a receiver and given to the originator.

Error Codes

Code	Description
1000	General exception
1001	Account settings required
1025	Config required
2000	General exception
2001	Payment not pending
2002	Payment not processing
2003	Sender payment not found
2004	Only inbound payments can be approved
2005	Receiver payment not found
2006	Only outbound payments can be canceled
2007	No active configuration found for account
2008	Origination not allowed for sender account type
2009	Origination not enabled for transaction type
2010	Max payment amount exceeded
2011	Custom sender name not allowed for account
2012	Receiver not found
2013	Origination not allowed to receiver account type
2014	Transaction type not enabled for receiver
2015	Sender and receiver accounts must be different
2016	Only inbound payments can be rejected
2100	Change not approved
2101	Change not pending
2102	Approval requires dual control
2103	Profile identifier already exists
2125	Change not approved
2126	Global profile not found or is invalid
2127	Change not pending
2128	Approval requires dual control
2129	Suspense Account not found
2150	Change not approved
2151	Change not pending
2152	Approval requires dual control
2153	Product required