This API enables you to get your webhook event details.

Endpoint: /cardmanagement/v1/3ds/{id}

GUID format card ID in the Cross River system, which is the id attribute value of the response to Create a card. This is not the number that appears on the card.

Product ID of the cardholder deposit account. This ID is in the GUID format. See also here.

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

partnerId

processorCardId

Deposit account number associated with the card

accountNumber

Card activation status:

- Unactivated
- Active
- Suspended
- Closed

status

Reason for the card status:

- NotSet
- Damaged
- Expired
- Lost
- FraudCompromised
- Return
- NewEnrollment
- Stolen
- AdminBlocked
- FraudBlocked

statusReasonCode

Status of the card in the processor's system

processorCardStatus

firstName

middleName

lastName

suffix

birthDate

shippingAddress

Address where the credit card bills are sent

billingAddress

Information about the cardholder's phone (type and number)

phone

emailAddress

nameOnCard

If defined, the name of the cardholder company

companyNameOnCard

Last 4 digits of the PAN, the primary account number, which appears on the physical card

panLastFour

ID of the previous card if the current card is a replacement

previousCardId

True if the PIN number is set for the card, otherwise false.

isPinSet

expirationDate

True if the card has been blocked by the administrator, otherwise false. This block cannot be removed.

adminBlocked

True, if the card was blocked by the processor due to potential fraud, otherwise false.

fraudSuspect

Unique ID for the card configuration profile the card is based on. You get this ID from Cross River. This ID is in GUID format.

configurationId

Type of card:

- Debit
- Credit
- Prepaid

paymentInstrument

The name of the card processor:

- i2c
- P1

processor

How the card is shipped:

- Normal
- Expedited

shippingType

Status of the card order:

- OrderPending (0)
- Completed (1)
- Failed (2)
- Authorizing (3)
- AuthorizationFailed (4)
- AuthorizationCompleted (5)

orderStatus

Indicates whether the card is a replacement card and the status of the replacement:

- NotApplicable
- Pending
- Completed
- Failed

replacementStatus

The unique Cross River ID assigned to a customer when the customer record is created. You need this ID to take action for a specific customer. For example, when opening an account or adding an address to a customer record.

The ID is in GUID format.

customerId

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

processorCustomerId

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

createdAt

Date and time when the card was suspended. If not suspended, null. In this case, the date and time are in this format: yyyy-mm-ddThh:mm:ss[.mmm]

suspendedAt

Date and time the card was closed. If not closed, null. In this case, the date and time are in this format: yyyy-mm-ddThh:mm:ss[.mmm]

closedAt

Date the card was activated. The time is set to midnight at the start of that day.

initialActivation

Exact date and time the card was activated. In this case, the date and time are in this format: yyyy-mm-ddThh:mm:ss[.mmm]

activatedAt

openedAt

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

The authentication ID obtained from the webhook callback (not from the authenticate response). This is a GUID format identifier that uniquely identifies a 3DS authentication session.

The unique identifier for this 3DS authentication session. GUID format. This value is sent to your webhook endpoint after calling simulate authenticate.

authenticationId

A unique string (32 hex characters) that identifies the transaction in a definite way. The payment card network passes this identifier, without changing it, throughout the entire interbank chain.

transactionId

Internal identifier for the step-up authentication request. Used to track the specific authentication attempt within the system.

stepUpRequestId

Counter which tracks the number of step-up authentication attempts made for this transaction. It increments with each retry attempt.

stepUpCounter

Select from the following types:

OTPSMS:  The customer receives a one-time password via SMS text message and enters it to authenticate the transaction.
OTPEMAIL: The customer receives a one-time password via email and enters it to authenticate the transaction.
OUTOFBANDOTHER: The customer authenticates using an external method (mobile app, phone call, etc.). Authentication must be explicitly validated via API using data from a webhook callback.


stepUpType

Token used internally for verification purposes. Generated by the system to validate the authentication flow.

verificationToken

Reference code associated with OTP-based authentication (OTPSMS or OTPEMAIL). Null for OUTOFBANDOTHER authentication type. Customer might this see code as reference in their SMS/Email.

otpReferenceCode

merchantId

merchantName

The URL/domain of the merchant's website. Used for fraud detection and customer awareness during authentication.

merchantUrl

ISO-defined 4-digit number that classifies a business by the goods they sell or the services they provide. nn characters maximum.

merchantCategoryCode

merchantCountryCode

GUID format card ID in the Cross River system, which is the ID attribute value of the response to Create a card. This is not the number that appears on the card.

cardId

Funds requested by the cardholder in the local currency of either the acquirer or source location of the transaction, exclusive of the transaction fee amount.

transactionAmount

This page explains how to retrieve 3DS details via the /cardmanagement/v1/3ds/{id} endpoint and highlights required webhooks and key session data.

Simulate tokenization completion

3DS authentication details

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.).

3DS authentication details

Relevant webhooks

API reference