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

If you are a PayFac merchant, you can now optionally optional a submerchant.url in the card verification request. This allows you to be compliant with scheme requirements.

You now receive a scheme reference in your card verification response irrespective of the outcome. We previously only returned this in verified responses. This advises you that a card was tokenized even though the card verification itself failed.

You can now send additional fund transfer type and purpose values in the fundsTransfer object in your verification request. This allow you to be compliant with card scheme requirements for fund transfers.

You can now send an optional billingAddress object in your verification request for card/token, card/networkToken and card/networkToken+ApplePay payment instrument types.

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. You must set this to true for any verifications made for the purpose of paying consumer bills in the future.

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.

New optional email and telephone fields in payment facilitator merchant block (24 August 2023)

Payment facilitator sub-merchant ID max length increased to 15 (16 August 2023)

New optional refusalAdvice field in verification refusal response (20 April 2023)

Additional fundingType values in response (v4 + v5) (01 March 2023)

New optional category field in response (v4 + v5) (01 March 2023)

ACH verification (v5) (07 November 2022)

Optional CVC field in the verification request (v5) (11 October 2022)

Merchant initiated transaction reason support on CardOnFile Endpoint (v5) (20 June 2022)

Cardholder name now an optional field (v5) (11 March 2021)

Updates to statement narrative in requests (v5) (15 February 2021)

Apple Pay decrypted verification (v4 + v5) (23 November 2020)

Additional card metadata fields in response (v4) (01 May 2020)

Version support for 3DS (v4) (07 February 2020)

Additional fields in response (v4) (27 January 2020)

cardOnFile verifications with tokens (v4) (31 December 2019)

oneTime verifications with tokens (v4) (20 November 2019)

Additional action link (v4) (20 November 2019)