Endpoint: /wires/v1/payments

The payment ID. First appears in the initial response to the originate a payment request. This ID is in GUID format.

Cross River Account number. In Cross River, depending on the account type, the number of digits will vary. The first digit indicates the kind of account.

accountNumber

Internal Cross River unique ID for the transaction

coreTransactionId

Unique Cross River reference ID for the payment

referenceId

Unique identifier in GUID format for the Federal Reserve batch the payment went out on (or came in on for inbound payments)

fedBatchId

fedBatchSequence

direction

Transfer, Drawdown, DrawdownResponse, ServiceMessage, Reversal

paymentType

Method used to send payment instructions: Phone, fax, email, file, API, partner portal, Ops portal.

source

Payment status: Created, Pending, Hold, Batched, Processing, Completed, Rejected, Canceled, Blocked

status

Posting status: Pending, Posted, Failed, Canceled

posting

Rejected because:
- OfacCancelUnableToDetermine
- OfacConfirmed
- OfacUnconfirmed
- Other

rejectionReason

blockedReason

Partner authorization for out-of-band payment requests: NotRequired, Pending , Approved, Canceled

partnerAuthorization

Date and time the wire was authorized. In this case, the date and time are in this format: yyyy-mm-ddThh:mm:ss[.mmm]

authorizedAt

Cross River user ID of the partner user who authorizes the wire

authorizedById

Cross River username of the partner user who authorizes the wire

authorizedByName

Second partner authorization for out-of-band payment requests: NotRequired, Pending , Approved, Canceled

partnerAuthorization2

authorizedAt2

authorizedById2

authorizedByName2

Dollar amount of wire transfer in positive integral cents. For example, write $1.00 as 100.

amount

currency

Reason for the wire transfer, such as "daily settlement." Also use this field if you submit multiple wires for the same amount, such as "1 of 2, 2 of 2." This data is not included with the outgoing FedWire message.

purpose

Input Messaging Accountability Data. A combination of a date, source identifier, and sequence number assigned to a Fedwire message when it is processed by the Federal Reserve Bank Funds Transfer application. Unique to the payment.

imad

Output Messaging Accountability Data. A combination of a date, destination identifier, and sequence number assigned to a Fedwire message when it is processed by the Federal Reserve Bank Funds Transfer application.

omad

The business purpose of the wire transfer. The most common type is customer wire transfer (CTR) where the beneficiary isn't a bank. See the full list of codes and descriptions.

businessFunctionCode

The type code value provides information about the type of wire transfer sent (type code, first 2 digits) and more details about the transfer (subtype code, second 2 digits).

typeCode

Fedwire routing number for the sender's bank

senderRoutingNumber

senderName

senderReference

The 9-digit Fedwire routing number of the financial institution receiving the wire drawdown request. The ABA directory provides financial institution routing numbers.

receiverRoutingNumber

receiverName

Details of the financial institution sending the wire

originatingFi

originator

Details of any intermediary bank involved in the wire transaction. Not all wire transfers use an intermediary FI.

intermediaryFi

Details of the financial institution receiving the wire

beneficiaryFi

beneficiary

Field for additional information from the originator to the beneficiary.

originatorToBeneficiary1

Optional field for additional information. 35 characters maximum.

beneficiaryReference

Month and day the wire was received in the format mmdd

receiptDate

Time the wire was received, in the format hhmm

receiptTime

True if the payment was reversed, otherwise false

wasReversed

True if the payment is international, otherwise false

isInternational

Use this attribute to add your own unique identifying string to a payment call or COS record. This attribute is useful for idempotency purposes.

clientIdentifier

Date and time the payment was created in the system. In this case, the date and time are in this format: yyyy-mm-ddThh:mm:ss[.mmm]

createdAt

Date and time the payment was released in a distribution to the Fed. In this case, the date and time are in this format: yyyy-mm-ddThh:mm:ss[.mmm]

releasedAt

Date and time the payment was processed by Cross River. In this case, the date and time are in this format: yyyy-mm-ddThh:mm:ss[.mmm].

processedAt

canceledAt

Date and time the payment was rejected. In this case, the date and time are in this format: yyyy-mm-ddThh:mm:ss[.mmm]

rejectedAt

Date and time the payment was blocked by BSA/AML. In this case, the date and time are in this format: yyyy-mm-ddThh:mm:ss[.mmm]

blockedAt

Business date on which the payment is effective

effectiveDate

Date and time the payment was systemically completed. This can only occur after the payment has successfully posted to the account. In this case, the date and time are in this format: yyyy-mm-ddThh:mm:ss[.mmm]

completedAt

Date and time the payment was posted to the Cross River account. In this case, the date and time are in this format: yyyy-mm-ddThh:mm:ss[.mmm]

postedAt

Payment ID of a previously sent wire that was reversed. Otherwise, the same as the payment ID.

originalPaymentId

Your unique ID in the Cross River system. This ID is in GUID format.

partnerId

ID in GUID format of your specific product type on which the account is based. Provided by Cross River. In this case, the Cross River account involved in the payment. More about Product IDs.

productId

Internal Cross River value. Date and time the database entry was last modified. In this case, the date and time are in this format: yyyy-mm-ddThh:mm:ss[.mmm]

lastModifiedAt

Includes OK (posted), RES (account restricted), NSF (insufficient funds in the account sending the wire)

postingCode

If Originator is null or empty, the system will use the configured account/product originator.

If the configured account/product originator contains any of the following ID codes, the request will be rejected:

Intermediary FI and Beneficiary FI Uniqueness

If both are specified with the same identifier, the request will be rejected.

IntermediaryFi and BeneficiaryFi cannot be identical.

Must be validated as a person or organization.

Errors follow the person/organization validation rules.

Must be validated as a financial institution.

Errors follow the financial institution validation rules.

Beneficiary FI (if not explicitly provided — no ID Code or Identifier specified)

Derived from the Receiver Routing Number:

Initiate a single wire transaction via POST /wires/v1/payments with sender, beneficiary, and funding details for domestic or international transfers.

Wires postal address update (November 2027)

Wire transfer

EKKO

ASHE

MORDEKAISER

AATROX

CRISTI_TEST

PREG

FDAT

International Organization for Standardization, a global organization that promotes commercial and industrial standards.

15-digit electronic ID number associated with the animal eartag

BDAT

CDAT

DairyComp 305 - VAS Dairy Management Software

DC305

DRPC

oocyte

Breeding Code

In-Vitro Fertilization. In relation to embryo transfers, IVF occurs when oocytes (eggs) are collected via OPU (ovum pick up), and then in a lab, semen is added to create embryos.

oocytes

National Association of Animal Breeders. www.naab-css.org

NAAB

EDAY

RPRO

SIRC

ETDAM

Vet Code 6 = ABT? Often if a dairy sees a pregnant animal showing signs of heat they may breed her. When this breeding is entered in DairyComp the animal remains pregnant, but this flag is set so that the veterinarian can determine if she is still pregnant to the original breeding or if she has aborted and is now just another "bred status" cow.

Vet Code 6 = ABT?

Dairy cattle typically have their hooves inspected and, if necessary, trimmed every 4–6 months. A strategic hoof-trimming program might evaluate hooves before first calving, between 60 and 150 days in milk, and before dry-off.

TRIM

hoof trim

A combination of ingredients used to make feed for animals

recipe

The dry weight of an ingredient with no mositure

DM/HD

BNAME

CNTL

VISID

The value that appears most often in a set of data.

Mode

SCPEN

Tech

Mastitis is the persistent, inflammatory reaction of the udder tissue due to physical trauma or infection. Symptoms of mastitis include udder swelling, heat, hardness, redness, or pain. The milk may have a watery appearance, flakes, clots, or pus.

Mastitis

mastitis

Metritis is inflammation of the wall of the uterus, and usually occurs within days of calving. Symptoms of metritis are an enlarged uterus and a foul-smelling uterine discharge.

metritis

Pneumonia is lung inflammation caused by a bacterial or viral infection. Early symptoms may include fever, depression, reduced appetite, nasal and eye discharge, salivation, shallow breathing, and soft coughing.

Pneumonia

Lameness includes any abnormality which causes an animal to change the way it walks, and can be caused by a range of foot and leg conditions, including hoof ailments, hock damage, bruising, sores, or cuts.

Lame

Diarrhea in young animals. Scours causes dehydration in calves and is the leading cause of death in calves under one month of age.

Scours

Retained placenta is the failure to expel fetal membranes within 24 hours after parturition. The primary symptom of a retained placental is degenerating, discolored, and ultimately fetid membranes hanging from the vulva.

Retained Placenta

Ketosis is a common ailment that usually occurs in early lactation, when the energy demands of milk production are very high and the cow metabolizes fat stores for energy. Symptoms of ketosis may include reduced milk yield, weight loss, reduced appetite, acetone smell of breath and/or milk, and fever.

Ketosis

Milk fever is a disease characterized by reduced blood calcium levels. It occurs in early lactation, when demand for calcium for colostrum and milk production exceeds the cow's ability to mobilize calcium. "Fever" is a misnomer, as body temperature during the disease is generally not elevated. Milk fever symptoms include tremor in the muscles of the head and limbs until falling to a "sitting" position. Once down, cows may have a dry muzzle, staring eyes, cold legs and ears, constipation, and drowsiness.

Milk Fever

Displaced abomasum in cattle occurs when the abomasum, also known as the true stomach, which typically resides on the floor of the abdomen, fills with gas and rises to the top of the abdomen, where it is said to be "displaced". Symptoms may include reduced appetite, lower milk yield, reduced rumination, and a distended abdomen.

Displaced Abomasum

EDAT

retained placenta

KPIs

The term "Zone" represents different dairy locations. Platform Zones may be different physical dairy locations (for example, multiple locations across the state or country) or different user-defined locations within a single dairy site (for example, Pens 1-100 are Zone 1, Pens 101-200 are Zone 2, etc.).

Zone

Allows you to manage the dairy's billing account for the VAS PULSE Platform.

Billing Management

Allows you to create new Dairy Dashboards and customize the widgets displayed on existing ones.

Dashboard Management

Dashboard View

Allows you to upload, download, and manage shared files, including the ability to create, edit, delete, and view file history details, in any domain.

File Management

Allows you to download and view history details for general shared files not associated with Herd, Feed, and Parlor data.

General

Allows you to manage Platform integration with other applications that send data to or extract data from Platform (for example, DairyComp for DC Unlimited subscribers, FeedComp, Parlors, and other allowed 3rd‑party software integrations).

Integration Management

Allows you to edit the dairy profile settings under Dairy Configuration > Dairy Information (dairy description, discoverability, address, etc.).

Profile Management

Allows you to invite new users, remove existing users, and manage role and permission settings for other users.

User Management

Allows you to create and manage dairy Zones. The term "Zone" represents different dairy locations. Platform Zones may be different physical dairy locations (for example, multiple locations across the state or country) or different user-defined locations within a single dairy site (for example, Pens 1-100 are Zone 1, Pens 101-200 are Zone 2, etc.).

Zone Management

Allows you to adjust dry matter % in FeedComp.

Wire transfer

Relevant webhooks

API reference

Validation Rules

Default Values