Card verification or Cardholder Name Inquiry.
Card Verifications (6)
Determine the validity of your customer's card to maximize authorization rates.
Authentication header
Authorization: {your_credentials}Replace {your_credentials} with your base64-encoded Basic Auth username and password given to your by your Implementation Manager.
You must use the Authorization header for any request you send to our Card Verifications API.
Accept/Content-Type header for card verifications
Content-Type : application/vnd.worldpay.cardVerifications-v6+json,
Accept : application/vnd.worldpay.cardVerifications-v6+jsonAccept/Content-Type header for ACH verifications (US accounts)
Content-Type : application/vnd.worldpay.achVerifications-v6+json,
Accept : application/vnd.worldpay.achVerifications-v6+json
We use the Accept header to identify which version of our API you are using. You must use the Accept header for any request you send to our Card Verifications API.
We require the Content-Type header if the request you're sending includes a request body, and if the HTTP method is a POST or a PUT.
DNS whitelisting
Whitelist the following URLs:
* https://try.access.worldpay.com/
* https://access.worldpay.com/
Please ensure you use DNS whitelisting, not explicit IP whitelisting.
Information about the merchant.
This should map to a profile from the Onboarding Domain. For more information contact your Relationship Manager or Implementation Manager.
A Merchant Category Code (MCC) can be applied to an individual request. You can only supply mcc, if we have enabled the dynamic MCC feature during boarding. If enabled but not provided, merchant.mcc defaults to a configured value. For more information contact your Relationship Manager or Implementation Manager.
A unique reference generated by you. It is used to identify a payment throughout its lifecycle.
64 characters max. We recommend your transactionReference contains between 9-20 characters for ease of onward processing.
If you are registered with Visa as a Consumer Bill Payment Service provider, you must set this to true for any verifications made for the purpose of paying consumer bills in the future.
Set this field to true to automatically retry a failed zero value verification with a nominal value authorisation amount. This is only possible if 0 or missing "value.amount" is submitted with the verification request. We automatically cancel the applied nominal authorization amount before your customer is charged.
Text to appear on the customer's billing statement. Sometimes referred to as a billing descriptor. If this isn't set, the value from your merchant profile is used.
An object that contains your customer's payment details.
- card/plain
- card/token
- card/networkToken
- card/networkToken+applepay
- card/networkToken+googlepay
- card/networkToken+samsungpay
An object that contains your customer's payment details.
Contains specific customer agreements for the transaction.
Contains specific customer agreements for the transaction.
The payment channel indicates the interaction of the cardholder with the merchant. Supply a value of moto to process an authorization as a Mail Order or Telephone Order transaction. When channel is not provided, the authorization will be processed as ecommerce ecom by default.
NOTE: 3DS authentication data cannot be supplied for MOTO payments.
- threeDS can apply OPTIONALLY to any paymentInstrument other than Apple Pay
- networkToken only applies to payment instruments: card/networkToken and card/networkToken+applepay networkToken should be mandatory for these instruments
- For paymentInstrument card/networkToken then the threeDS object can optionally be supplied along with the networkToken one
The details of the recipient of the payment.
We highly recommend you supply this, if your MCC is 6012 or 6051. Sending this field ensures you remain PSD2 compliant and avoid potential acquirer refusals.
- Test (Try)https://try.access.worldpay.com/cardVerifications
- Livehttps://access.worldpay.com/cardVerifications
- Payload
- curl
- Python
- Java
- Node.js
- Go
- PHP
- Ruby
- C#
- Successful card verification for payfac and card on file
- Successful card verification with a token
- Successful card verification with a token, 3DS data and customer agreement
- Successful card verification with a network token
- Successful card verification for one-time and nominal retry
- Successful card verification for one-time with no nominal retry
- Successful card verification with 3DS2 values
- Successful card verification with optional fund transfer values
- Successful card verification with Apple Pay decrypted
- Successful card verification with Google Pay decrypted
- Successful card verification with Samsung Pay decrypted
- Successful cardholder name inquiry with card details
- Successful cardholder name inquiry with a token
{ "type": "cardVerification", "merchant": { "entity": "default", "mcc": "6012", "paymentFacilitator": { "schemeId": "12345678901", "independentSalesOrganizationId": "12345678901", "subMerchant": { "name": "Merchant Plc", "reference": "12345", "address": { "street": "123 Street", "state": "CA", "city": "San Francisco", "countryCode": "US", "postalCode": "94101" }, "taxReference": "12345", "phoneNumber": "0123456789", "email": "test@email.com", "url": "developer.worldpay.com" } } }, "transactionReference": "Memory265-13/08/1876", "instruction": { "value": { "amount": 250, "currency": "GBP" }, "narrative": { "line1": "MindPalace", "line2": "Memory" }, "customerAgreement": { "type": "cardOnFile" }, "paymentInstrument": { "type": "card/plain", "cardHolderName": "Sherlock Holmes", "expiryDate": { "month": 5, "year": 2050 }, "cardNumber": "4444333322221111", "billingAddress": { "address1": "221B Baker Street", "address2": "Marylebone", "address3": "Westminster", "postalCode": "NW1 6XE", "city": "Cambridge", "countryCode": "GB" }, "cvc": "101" } } }
- Matched name inquiry (verified result)
- Matched name inquiry including risk factors (verified result)
- Matched name inquiry and declined CVC (not verified result)
- Card unsupported for name inquiry and not verified result
{ "outcome": "verified", "nameInquiry": "matched" }
Possible values: checking, savings, corporate, corporateSavings.
- Test (Try)https://try.access.worldpay.com/achVerifications
- Livehttps://access.worldpay.com/achVerifications
- Payload
- curl
- Python
- Java
- Node.js
- Go
- PHP
- Ruby
- C#
- Successful account verification outcome.
- Refused account verification outcome.
{ "merchant": { "entity": "default" }, "transactionReference": "1234567", "paymentInstrument": { "type": "bankAccountUS", "accountType": "corporateSavings", "accountNumber": "1234567890", "routingNumber": "011400495", "companyName": "companyName", "billToAddress": { "firstName": "John", "lastName": "Smith", "address1": "address1", "address2": "address2", "address3": "address3", "city": "city", "region": "state", "postalCode": "postalCode", "countryCode": "US", "telephoneNumber": "4085551212" } } }
- Successful account verification outcome.
- Refused account verification outcome.
{ "outcome": "verified", "checkedAt": "2021-09-27T18:02:16.475Z" }
- Test (Try)https://try.access.worldpay.com/cardVerifications/{linkData}
- Livehttps://access.worldpay.com/cardVerifications/{linkData}
- Payload
- curl
- Python
- Java
- Node.js
- Go
- PHP
- Ruby
- C#
No request payloadSuccessful query request
Card issuer's scheme (not all issuers return this)
List of risks involved in this verification.
A bank identification number is the first four to six numbers that appear on payment cards.
- Querying of a successful verification for oneTime
- Querying of a successful verification for cardOnFile
- Querying of a refused verification
Querying of a successful verification for oneTime
{ "outcome": "verified", "checkedAt": "2018-09-01T10:37:36.923Z", "riskFactors": [ { "risk": "matched", "type": "cvc" }, { "risk": "matched", "detail": "postcode", "type": "avs" }, { "risk": "matched", "detail": "address", "type": "avs" } ], "paymentInstrument": { "type": "card/plain+masked", "cardBin": "444433", "lastFour": "1111", "countryCode": "GB", "expiryDate": { "month": 12, "year": 2029 }, "brand": "visa", "fundingType": "debit", "issuerName": "cardIssuer", "category": "consumer", "paymentAccountReference": "reference" }, "_links": { "cardVerifications: verification": { "href": "https://try.access.worldpay.com/cardVerifications/{resource}" } } }