# Verifone Test Payment Cards

HTML version: [Verifone Test Payment Cards](https://support.gladstonesoftware.cloud/kb/verifone-test-payment-cards)

## Problem
You need test payment card details and transaction values to simulate different transaction outcomes (approved, declined, declined due to communications down) and PIN scenarios on a Verifone [PED](../guides/glossary.md) (Pin Entry Device, the card payment terminal) for both Customer Present and Customer Not Present transactions.

## Resolution

### Simulating Transaction Values
Different values can be used to force specific payment responses when testing:

1. **Transaction Approved:**  
   - End the transaction value with a `0` (e.g., £1.00).
2. **Transaction Declined:**  
   - End the transaction value with a `5` (e.g., £1.05).
3. **Transaction Declined (COMMS_DOWN):**  
   - End the transaction value with a `7` (e.g., £1.07).

### Simulating PIN Responses
Use the following PINs to force specific terminal responses:

- `1234` — PIN validation successful.
- `5678` — PIN is Invalid. One try left.
- `1122` — Blocked PIN. Rolls forward to signature validation.

### Customer Not Present Test Card Details

Use these details for testing Customer Not Present transactions on a V200c PED:

- **Card Number:** `4444333322221111`
- **Expiry Date:** Any future date
- **CSC/CVV/CVC/CID:** `000000` (returns a "matched" response*)
- **Address Number:** `1010` (returns a "matched" response*)
- **Postcode:** `156156` (returns a "matched" response*)

\* Other values for CSC, address, or postcode can be entered, but will return an "unmatched" response.

## Notes

- CSC, CVC, CVV, CID all refer to the 3- or 4-digit security number on a payment card. The term used depends on the card provider:
  - **CSC:** Card Security Code (American Express)
  - **CVC:** Card Validation Code (Mastercard)
  - **CVV:** Card Verification Value (Visa)
  - **CID:** Card Identification Number