Relaxed Requirements for Address Data and Expiration Date in Payment Transactions
With relaxed requirements for address data and the expiration date, not all standard payment request fields are required. It is your responsibility to determine whether your account is enabled to use this feature and which fields are required.
Requirements
You must contact customer support in order to enable relaxed requirements for address data and expiration date.
Services
Relaxed requirements for address data and expiration date are supported for these services:
-
Authorization
-
Capture
-
Stand-alone credit
-
Subscription create
-
Subscription update
Relaxed Fields
IMPORTANT
When relaxed requirements for address data and expiration date are enabled for your
Cybersource
account, and your service request does not include one or more of the fields in the following list, you increase the risk of declined transactions and fraud depending on your location, your processor, and the cardholder's issuing bank.
It is your responsibility to determine whether a field is required for the transaction you are requesting. For example, an issuing bank can decline an authorization request for a recurring transaction with a Visa Europe card if the expiration date is incorrect, invalid, or missing. If you do not provide the correct expiration date for a recurring transaction the authorization request may be declined.
-
When you include this field in your request, you must also includepaymentInformation.card.expirationYear.
-
You can submit an expiration date that has expired. This exception does not apply when you combine any of the services listed above with any other service.
-
This field is required for payment network token transactions and subscription creation requests.
-
When you include this field in your request, you must also includepaymentInformation.card.expirationMonth.
-
You can submit an expiration date that has expired. This exception does not apply when you combine any of the services listed above with any other service.
-
This field is required for payment network token transactions and subscription creation requests.