Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
NameValuePair object.
| Data Members | Data Type | Description |
|---|---|---|
name | string | Required. The name for the name/value pair. |
value | string | Required. The value for the name/value pair. |
vin:. These pairs are listed and defined in the nameValue data member for the specified object.
| Feature | Name | Description | Relevancy |
|---|---|---|---|
| Transaction object- Card on File Indicator for every transaction that stores customer card information. | vin:SciToken | If your payment processor is supporting CIT/MIT information, include the Network Token (as this NVP) that you received from your processor’s for the successful authorization of the subscription creation. The following are examples of field names that hold this value in the different Payment Provider environments: - CyberSource:ccAuthReply_paymentNetworkTransaction - Orbital/Stratus:TXID/NRID - SmartPay:schemeReferenceData - Vantiv Litle:Transaction Id | Required for CIT/MIT |
| Transaction object- an indicator whether the payment method is a network token | vin:isNetworkToken | A boolean indicating whether network tokens are passed for the paymentMethodId. Supported for: Chase paymentech - A value of 1 should be used when network tokens are passed. | Required for Network Tokens |
| Transaction object- the cryptogram the merchant requested for the network token Transaction. | vin:NWTCryptogram | An indication whether a cryptogram is passed as part of network tokens usage.Supported for: Chase paymentech - enter the cryptogram string in the value attribute. Note: If cryptograms are not retrieved by the merchant, do not include this Name-Value Pair. | Optional. Required only for network tokens with cryptograms |
| Parent topic:The NameValuePair Object |