Skip to main content

Simulate Authorizations and Refunds

Simulation card data

test with dummy data

Do not enter production data in the Highnote Test environment, which is for exploring features and training. Use only dummy or test data.

To test your payments integration, you can use test Primary Account Numbers (PANs), addresses, and CVCs to simulate various scenarios, including specific card brands, error code responses, and successful payments.

We currently support simulation card data for the following brands:

Card NetworkPANCVV/CVCExpirationAddress
Visa4000 0000 0000 0002111Any future date1234 Visa St, Visa, CA 12345
Mastercard5555 5555 5555 4444222Any future date2134 Mastercard St, Mastercard, CA 21345

Simulate successful authorization

To simulate a successful authorization, use the following inputs in your payment form:

  • A valid simulation PAN
  • A valid simulation CVC
  • Any valid future expiration date
  • A valid simulation postal code

Use the corresponding simulation values of the card network of your choosing for each of the required inputs by referencing the simulation card data table above.

Simulate declines

The following transaction amounts will generate specific decline codes for cards. Set the desired card network using the simulation card data listed above:

Error Code ResponseAmountsRetries Allowed
DO_NOT_HONOR$1.11Allowed
INVALID_CARD_NUMBER$2.22Not Allowed
INSUFFICIENT_FUNDS$3.33Allowed
EXPIRED_CARD$4.44Not Allowed
BAD_CVV2$6.67Not Allowed
UNACTIVATED_CARD$7.77Allowed
SUSPENDED_CARD$8.88Not Allowed
TERMINATED_CARD$9.99Not Allowed
INVALID_AUTHORIZATION_EXPIRATION$11.11Not Allowed
BLOCKED_CARD$22.22Allowed
TRANSACTION_NOT_PERMITTED$33.33Not Allowed
RE_ENTER_TRANSACTION$44.44Allowed
CLOSED_ACCOUNT$55.55Not Allowed
SPECIAL_CONDITION_NO_PICK_UP$66.66Allowed
INVALID_MERCHANT$77.77Allowed
INVALID_TRANSACTION$88.88Not Allowed
EXCEEDS_APPROVAL_AMOUNT_LIMIT$99.99Allowed
EXCEEDS_WITHDRAWAL_FREQUENCY_LIMIT$111.11Allowed
RESTRICTED_LOCATION$222.22Allowed

Simulate refund declines

Refunds in the Highnote API are processed as a PaymentCreditTransaction. Unlike authorizations, there are no dedicated refund event types. Instead, refund outcomes are represented using the following events:

Refund outcomeEvent
ApprovedCardPaymentAuthorizedEvent
DeclinedCardPaymentAuthorizationDeclinedEvent

To simulate a declined refund, use the refundPaymentTransaction mutation with one of the decline amounts from the Simulate declines table above. For example, a refund amount of $1.11 triggers a DO_NOT_HONOR decline.

To simulate an approved refund, use any amount that is not in the decline amounts table and does not exceed the captured amount of the original transaction.