Versioning and Change log

The new Card Verifications API introduces a new single endpoints and consistent JSON structure to simplify your integration.

• removal of separate endpoints for intelligent and dynamic verifications
• field value based routing for one time vs card on file
• request and response field name changes to align with industry standard
• added support for network payment tokens
• added support for AFT related optional fields

• you must now submit narrative in your intelligent and dynamic verification request
• this is no longer a breaking change. narrative is now an optional field as of 02/15/2021

• header change to "Content-Type: application/vnd.worldpay.verifications.accounts-v4+json"
• sending any fields not recorded in our documentation returns an error

• header change to "Content-Type: application/vnd.worldpay.verifications.accounts-v3+json"
• new mandatory transactionReference field

• header change to "Content-Type: application/vnd.worldpay.verifications.accounts-v2+json"
• verifications:recurring action link and https://try.access.worldpay.com/verifications/accounts/intelligent/recurring resource link removed
• cardOnFile endpoint now returns cardOnFileAuthorize and recurringAuthorize action links in the response
• merchant.reference renamed to merchant.entity
• billingAddress renamed to verificationAddress

You can now make a nameInquiry for Visa cards with our Card Verifications API. This allows you to check the validity of the cardholder name provided.

You can now send a channel field within your request.

You can now send a consumerBillPayment flag within the instruction object in your request. Customer's of Visa's Consumer Bill Payment (CBP) service must set this to true.

You now have the option to send a recipient object within your Verification request. You should send this if your MCC is 6012 or 6051 to remain PSD2 compliant and avoid acquirers refusing your payment.

You now have the option to send an email and telephone field within your payment facilitator merchant object.

The paymentFacilitator merchantId now has a maximum digit length of 15. The previous limit was 7.

You will now receive a Merchant Advice Code (MAC) as overrideName in the not verified response, if you have requested to receive this.

The field fundingType in the paymentInstrument object of your response can now have the following additional values:

• `chargeCard`
• `prepaid`
• `deferreddebit`

We have added these to the already existing values of debit and credit.

You now have an additional field of category in the card section of your oneTime response if you have opted in to receive it. This field populates data from the cardbin:productType field value.

• You can now send verification requests against US bank accounts to ACH endpoint:

  • https://try.access.worldpay.com/verifications/accounts/ach

• You can now submit the CVC as an optional field in the verification request with token for both oneTime and cardOnFile endpoints.

  • https://try.access.worldpay.com/verifications/accounts/intelligent/oneTime
  • https://try.access.worldpay.com/verifications/accounts/intelligent/cardOnFile
  • https://try.access.worldpay.com/verifications/accounts/dynamic/oneTime
  • https://try.access.worldpay.com/verifications/accounts/dynamic/cardOnFile

• You can now supply storedCredentials.reason as an optional field for both cardOnFile endpoints:

  • https://try.access.worldpay.com/verifications/accounts/intelligent/cardOnFile
  • https://try.access.worldpay.com/verifications/accounts/dynamic/cardOnFile

• The paymentInstrument.cardHolderName field is no longer mandatory in v5 requests.

• The narrative block is no longer a mandatory field in v5 requests to cater for upstream services

You can now submit your v4 and v5 intelligent and dynamic verification with a decrypted Apple Pay paymentInstrument. This only applies to the cardOnFile endpoints:

https://try.access.worldpay.com/verifications/accounts/intelligent/cardOnFile

https://try.access.worldpay.com/verifications/accounts/dynamic/cardOnFile

• we are returning paymentInstrument in verified and notVerified responses for enabled merchants

• you can now submit the following values for authentication.version in your 3DS request:

  • for 3DS1 - 1.0.2
  • for 3DS2 - 2.1.0 or 2.2.0

• we are returning riskFactors in verified and notVerified responses

• you can now send verification requests with a token to both cardOnFile endpoints:

  • https://try.access.worldpay.com/verifications/accounts/intelligent/cardOnFile
  • https://try.access.worldpay.com/verifications/accounts/dynamic/cardOnFile

• you can now send verification requests with a token to both oneTime endpoints:

  • https://try.access.worldpay.com/verifications/accounts/intelligent/oneTime
  • https://try.access.worldpay.com/verifications/accounts/dynamic/oneTime

• recurringSale action link is now returned in the cardOnFile verification responses. This allows for recurring sale transactions.