EVevervault
Payments
Real-time Account Updater

Simulate an Account Updater Check

Simulate a card check so you can test your integration without a real query to the card networks. Provide the test card 4242424242424242 and the type of result you want returned.

The response is an Account Updater Check, identical in shape to a live check. A new-account-number result returns 4111111111111111 as the replacement card, as an Evervault encrypted string.

Checks can only be simulated for the test card 4242424242424242. Any other card returns a 400 response.

This endpoint is only available to Sandbox apps.

post/payments/cards/checks/simulate

Request

Request body

type'no-change' | 'new-expiry-date' | 'new-account-number' | 'account-closed' | 'contact-cardholder' | 'cardholder-opt-out' | 'merchant-opt-out' | 'no-match' required

The check result to simulate. Accepts any of the results a live check can return.

Example request

{
  "card": {
    "number": "4242424242424242",
    "expiry": {
      "month": "12",
      "year": "29"
    }
  },
  "type": "new-account-number"
}

Response

The simulated check completed.

idstring required

The unique identifier for the check.

result'no-change' | 'new-expiry-date' | 'new-account-number' | 'account-closed' | 'contact-cardholder' | 'cardholder-opt-out' | 'merchant-opt-out' | 'no-match' required

The outcome of the check. Only new-expiry-date and new-account-number carry an update payload; every other result returns no new credentials.

Example response

{
  "id": "auc_8da9a7fbde01",
  "result": "new-account-number",
  "update": {
    "card": {
      "number": "ev:debug:Tk9D:number:nTepvAI585M7lUVp:AkJ6Brzat0E7ui8DSKCSXO7AopU/+GFuBekQ6cGx7eTl:sfihK53itmHp+URxomnTITUpwQwM5nnRrnQ0qdIOUlA=:$",
      "expiry": {
        "month": "12",
        "year": "29"
      }
    }
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.