Integration
The common elements of any of our integrations consist of the choice of the environment and API credentials.
As with most current platforms, we provide an integration environment, also known as sandbox, and a production environment known as live. Typically, switching between environments involves changing the server address where we make the calls.
In our online payment (ecommerce) solutions, you will have access to an address for the environment:
- sandbox.sipay.es - testing and integration environment
- live.sipay.es - production environment
and the API credentials:
- key: used to identify the merchant
- resource: associated with specific configuration such as the bank where settlements are made, payment method activation, etc.
- secret: key for digitally signing your calls to prevent anyone from impersonating your transactions
The in-person payment product integration will use client, establishment, and point of sale identifiers to perform transactions. Additionally, you will need to activate the service with one of our agents. The intermediary software between the card reader device, the gateway, and the point of sale, which we call DeviceHub, will have an environment selector where we will conduct the operations.
Further on, you will find specific information on how to use them.
Integration Methods
From our point of view, the most important aspect of integrating a payment technology product is to create a balance between user experience and security.
We recommend analyzing your business processes and deciding how to integrate our online or in-person payment products.
Our integration methods are inspired by a technical aspect that defines their behavior and implementation method:
- Hosted Payment Page HPP: the user will be redirected to a pre-designed payment page.
- Components: allows the merchant to build their own payment experience.
- API: this is the most basic level of integration and the foundation for all the above options. It is available for Merchants who need maximum customization.