3DS ReferenceProtocol & field guide

EMV 3-D Secure · Core specification 2.3.1.1

Recurring DaterecurringDate

Recurring Date in Authentication Request (AReq).

Source edition: Core 2.3.1.1 · Type: String · Length: 8 characters · Minimum length: 8 · Maximum length: 8

Baseline in AReq Conditional

Conditional. Same classification across the remaining channels and categories. Required if Recurring Indicator/ Frequency Indicator = 01. Usage and conditions ↓

Explore in context →

Usage in AReq

Effective date of the new authorised amount following the first/promotional payment in a recurring or instalment transaction.

Conditional inclusion — source text

Required if Recurring Indicator/ Frequency Indicator = 01.

Related condition fields: recurringInd.

Format and scope

Type: String · Length: 8 characters · Minimum length: 8 · Maximum length: 8

Source components: 3DS Server. Channels: 01-APP, 02-BRW, 03-3RI. Categories: 01-PA, 02-NPA.

EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 275

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.

Explore in context →

Sources and related references

EMV_3DS_CoreSpec_v2.3.1.1_20230530.pdf, Table A.1, PDF pages 275

Source review status: carried-forward. Carried-forward material has not acquired a new verification claim.

Document fingerprint (SHA-256): 6fdf0aba3fc1a765f96b74dad4069d1e189969f38f0023647021687daf589d6b