Table Of Contents

1.1. Introduction

1.1.1. Pre-conditions to use the SysPay API

A new merchant must provide us with:

  • Event Messaging Service URL. This is the URL you will receive notifications to. (Payments, refunds, chargebacks, etc..)
  • Redirect URL. This is the URL the customer will be redirected to after the payment has been processed on our hosted payment page.
  • The IP-addresses of the servers that are going to call the webservices API.

We will provide the merchant with:

  • An API login.
  • A secret passphrase that is shared between SysPay and the merchant and used to build the authentication headers and validate the EMS notifications.

1.1.2. Sandbox and live system

The SysPay Sandbox is a self-contained environment within which you can prototype and test SysPay features and APIs. The SysPay Sandbox is an almost identical copy of the live SysPay system. Its purpose is to give developers a shielded environment for testing and integration purposes and to help avoid problems that might occur while testing SysPay integration solutions on the live site. Before moving any SysPay-based application into production, you should test the application in the Sandbox to ensure that it functions as you intend.

The only difference between the Sandbox and the live system is the URL: