Skip to main content

Testing, certification and error codes

Testing and sandbox accounts​

As part of any integration, Pepper will provide a sandbox account which may be used for testing the end to end integration. This sandbox account will include:

  • Access to the Pepper API's for the sandbox merchant
  • Access to the Pepper console for the sandbox merchant to manage orders and payments
  • A web or mobile app which can be used to sign up loyalty users and test redemptions
  • A sample set of Perks configured to match the anticipated use cases of any pilot merchants

To allow an efficient and robust end to end platform, the following dependencies must be met:

  • Before beginning work on an integration, the POS provider must provide Pepper with:
    • Access to a POS sandbox which is capable of emulating the end to end journey. E.g. a POS terminal working on a sandbox account which can be connected to the Pepper Sandbox tenant
    • A description of the use cases and user journeys that the integration will create (e.g. will search be supported, or just bar-code scanning)
    • A project/delivery plan which allows Pepper to assign relevant resource for testing
  • Prior to launching with a pilot merchant, Pepper and the POS provider will agree a list of test cases which must be met, which will be mutually tested.
  • After launch with a pilot merchant, extended support must be provided by both Pepper and the POS provider until both parties agree that the integration is stable and production ready, with daily review of logs and errors and an agreed escalation path to developers.

Testing Payments​

The PepperPay gateway uses Stripe for completing payments. Any standard Stripe test card can be used, including those for testing error cases, such as declined cards.