Download the PHP package worldline/sips-payment-sdk without Composer
On this page you can find all versions of the php package worldline/sips-payment-sdk. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package sips-payment-sdk
:warning: As of 30/06/2021 the sips-atos.com urls will stop working. they have been replaced by sips-services.com urls. Make sure to update to version 1.0.7 or higher to avoid problems.
Sips Library
This package provides a PHP implementation for Sips, the Worldline e-payments gateway.
:warning: This library was written for Sips 2.0 and is not comptible with Sips 1.0!
Installation
The recommended way to install this Sips Library is through Composer.
Run the composer commmand to install the latest stable version of the package:
After installing the package, you need to require Composer's autoloader:
Usage
:bulb: Currently the library only supports Sips in paypage mode.
Initialization
First, create a client for the desired environment using your merchant ID, key version & secret key.
Next, set up the request to initialize a session on the Sips server.
Add a unique reference for the transaction.
:bulb: If no reference is provided by you, the plugin will generate one.
And finaly submit the request to the server to initialize the transaction.
The initializationResponse you'll receive from the server contains all information needed to continue handling the transaction.
If your initialization was successful, your response will contain redirectionStatusCode = '00'
Redirection to the paypage
In case your initialization was successful, you have to use the redirectionUrl received to perform a POST request with both the redirectionData and seal as parameters. Since this should redirect the customer to the Sips payment page, the cleanest example is a simpleHTML form:
Verifying the payment
When the customer is done, he will be able to return to your application. This is done via a form, making a POST request to the normalReturnUrl provided during the initialization of your payment.
This POST request contains details on the payment.
You can simply decode these responses and create a PaypageResult object by calling the finalizeTransaction function:
:warning: Since the customer is not always redirecting back (e.g. he closes the confirmation page), it's a good practice to include an
automaticResponseUrl. Sips will always POST details of the transaction to this URL, even if a customer doesn't redirect back to your website.
