Skip to content

Testing

TESS Payments edited this page Nov 30, 2022 · 1 revision

This page describes the TESS Payments Android SDK Testing guide.

Please note, that all transactions will be processed using Test engine.

AkuratecoTestCard

1. AkuratecoTestCard.SALE_SUCCESS

This card number and card expiration date must be used for testing successful sale:

  • Response on successful SALE request: "action": "SALE", "result": "SUCCESS", "status": "SETTLED".
  • Response on successful AUTH request: "action": "SALE", "result": "SUCCESS", "status": "PENDING".

2. AkuratecoTestCard.SALE_FAILURE

This card number and card expiration date must be used for testing unsuccessful sale:

  • Response on unsuccessful SALE request: "action": "SALE", "result": "DECLINED", "status": "DECLINED".
  • Response on unsuccessful AUTH request: "action": "SALE", "result": "DECLINED", "status": "DECLINED".

3. AkuratecoTestCard.CAPTURE_FAILURE

This card number and card expiration date must be used for testing unsuccessful CAPTURE after successful AUTH:

  • Response on successful AUTH request: "action": "SALE", "result": "SUCCESS", "status": "PENDING".
  • Response on unsuccessful CAPTURE request: "action": "CAPTURE", "result": "DECLINED", "status": "PENDING".

4. AkuratecoTestCard.SECURE_3D_SUCCESS

This card number and card expiration date must be used for testing successful sale after 3DS verification:

  • Response on VERIFY request: "action": "SALE", "result": "REDIRECT", "status": "3DS".
  • After return from ACS: "action": "SALE", "result": "SUCCESS", "status": "SETTLED".

5. AkuratecoTestCard.SECURE_3D_FAILURE

This card number and card expiration date must be used for testing unsuccessful sale after 3DS verification:

  • Response on VERIFY request: "action": "SALE", "result": "REDIRECT", "status": "3DS".
  • After return from ACS: "action": "SALE", "result": "DECLINED", "status": "DECLINED".