Originate a drawdown request
An outbound wire drawdown request, also called a reverse wire, asks a someone to send funds back to you as the requester.
In this tutorial, you'll learn how to:
✅ Send a drawdown request
If you are new to wires we recommend you read the Wires overview documentation before starting this tutorial.
The tutorial assumes you have a knowledge of APIs and how they work. For more information on sending API calls, see the API overview.
For this tutorial you'll need to understand these terms. These definitions are specific to this tutorial. The terms might be used slightly differently for a drawdown response.
Term | Description |
|---|---|
Originator | The entity requesting the payment |
Beneficiary | The entity receiving the payment |
Originating financial institution | The financial institution wherethe payment request comes from |
Intermediary financial institution | A financial institution that a payment is routed through (required for international wires, otherwise not always needed) |
Beneficiary financial institution | The financial institution that receives the payment request |
Drawdown Credit Account NumberSending financial institution | The financial institution that sends the payment request 9 digit routing/ABA number of the originating financial institution |
Receiveringfinancial institutionRoutingNumber | The routing number of the financial institution that receives the payment request |
Drawdown request | A request for someone to send a payment by wire |
The tutorial uses these API endpoints:
API | Description |
|---|---|
Requests an inbound wire transfer |
The tutorial uses these webhooks.
Webhook | Description |
|---|---|
Wire.Payment.Sent | Outbound wire has been transmitted to the Federal Reserve and has been successfully acknowledged. IMAD number is now available. |
Wire.Payment.Received | Inbound wire payment received successfully. |
Wire.Payment.Rejected | Outbound wire could not be processed due to compliance reasons or was rejected by the Federal Reserve. |
Make sure you have:
- Account number of the account requesting the payment
- Receiver routing number
To receive the webhook events for this tutorial both partner accounts need to register each specific webhook event type. Once you are registered, the event objects are sent to the registered URLs.
The event object contains a list of resource identifiers used to download details on each event.
When you initiate an outbound wire drawdown request (DRC 1031), the request is sent to the specified bank where the account responsible for the payout is held. The bank's response includes the payment status and other relevant information about the request. Webhook events are triggered when specific payment statuses are set.
In this tutorial, the PMR Corporation requests a $500,000 wire payment from Lindberg Incorporated.
If you want to enter originator values yourself (instead of the system populating those attributes based on your account number), ensure that Allow Custom Originator is enabled on the product or account .
Call POST /v1/payments/corporate-drawdown-requests. For this call, some/all attributes are required. A full list of attributes is found here.
We recommend that you save the request-id, you can see in the response header to use if you need to contact the Cross River Support Team about that specific call. See Response headers for more detail about this unique ID.
A successful API call returns a JSON response with the details of the drawdown request.
Successful posting of the payment triggers the wire.payment.received webhook event.
