Usage in AReq
Indicates whether the recurring or instalment payment has a fixed or variable amount and frequency. The Recurring Indicator object contains: • the Amount Indicator • the Frequency Indicator Example: {"recurringInd":{ "amountInd":"01", "frequencyInd":"02"} }
Conditional inclusion — source text
Required if: • 3DS Requestor Authenticati on Indicator = 02 or 03; OR • 3RI Indicator = 01 or 02
Related condition fields: threeDSRequestorAuthenticationInd, threeRIInd.
Format and scope
Type: Object
Source components: 3DS Server. Channels: 01-APP, 02-BRW, 03-3RI. Categories: 01-PA, 02-NPA.
Object members
Nested presence rules apply when the parent is supplied. Consult the source for full conditions.
amountInd — Amount Indicator
Indicates whether the recurring amount is fixed or variable
Type: String · Length: 2
| Value | Meaning | Introduction tag |
|---|---|---|
01 | Fixed Purchase Amount | Not tagged |
02 | Variable Purchase Amount | Not tagged |
03–79 | Reserved for EMVCo future use (values invalid until defined by EMVCo) | Reserved |
80–99 | Reserved for DS use | Reserved |
Introduction tags are shown where recorded. An absent tag does not establish when a value was introduced.
frequencyInd — Frequency Indicator
Indicates whether the recurring frequency is fixed or variable
Type: String · Length: 2
| Value | Meaning | Introduction tag |
|---|---|---|
01 | Fixed Frequency | Not tagged |
02 | Variable or Unknown Frequency | Not tagged |
03–79 | Reserved for EMVCo future use (values invalid until defined by EMVCo) | Reserved |
80–99 | Reserved for DS use | Reserved |
Introduction tags are shown where recorded. An absent tag does not establish when a value was introduced.
EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 277
Scoped FAQ qualifications
- FAQ 27 — Applicable object-bearing protocol versions
Only when the parent JSON object is present
Evaluate nested presence conditions when the parent object is present. In multiTransaction, merchantList is required when the object is supplied; merchantAmount remains optional.
- FAQ 73 — Applicable object-bearing protocol versions
An optional or conditionally optional field is sent empty
An empty optional field produces error 203 under Req 309. When the empty JSON object contains mandatory data, error 201 may be returned.
Transaction context
This reference covers the published source edition. Use the explorer to inspect this field and any applicable transaction conditions. Scheme programme requirements are not inferred from the protocol edition.
Sources and related references
EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 277
Source review status: carried-forward. Carried-forward material has not acquired a new verification claim.
Document fingerprint (SHA-256): 6fdf0aba3fc1a765f96b74dad4069d1e189969f38f0023647021687daf589d6b