Download the PHP package ang3/php-psp-systempay-client without Composer
On this page you can find all versions of the php package ang3/php-psp-systempay-client. 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 php-psp-systempay-client
PHP Systempay PSP Client
PHP HTTP client for Systempay PSP.
Installation
Open a command console, enter your project directory and execute the following command to download the latest stable version of the client:
This command requires you to have Composer installed globally, as explained in the installation chapter of the Composer documentation.
Usage
Configure API Credentials
The API client requires credentials for authentication. You can use the provided demo credentials or create your own:
Instantiate the API Client
Pass the credentials (and optionally a PSR-3 logger) to the ApiClient:
Making a Request
Use the request method to send a POST request to the Systempay API.
What Happens Under the Hood
- Endpoint: The API endpoint is determined by the provided enum or string.
- HTTP Request: The client sends a POST request with the JSON encoded payload.
- Authentication: Basic authentication is handled using the credentials (username and API key).
- Response Parsing: The API response is parsed into an ApiResponse object.
- Logging: If a logger is provided, details of the request (including a unique request ID, endpoint, and payload) are logged.
Error Handling
The request method may throw several exceptions:
Symfony\Contracts\HttpClient\Exception\DecodingExceptionInterface: Thrown when the response cannot be decoded.Symfony\Contracts\HttpClient\Exception\TransportExceptionInterface: For network-related errors.Symfony\Contracts\HttpClient\Exception\RedirectionExceptionInterface: For 3xx HTTP responses (if the maximum redirects are reached).Symfony\Contracts\HttpClient\Exception\ClientExceptionInterface: For 4xx HTTP responses.Symfony\Contracts\HttpClient\Exception\ServerExceptionInterface: For 5xx HTTP responses.Ang3\Component\PSP\Systempay\Exception\InvalidResponseException: Thrown if the API response payload is invalid.
Ensure to catch these exceptions to handle errors gracefully.
IPN Payload Validation
Before processing an IPN (Instant Payment Notification) from Systempay, you should validate the payload using the validatePayload method provided by the API client.
This method ensures that the payload conforms to Systempay’s expected structure, includes all necessary data, and that its integrity is verified by checking the hash signature. It accepts an associative array (or a Payload object) and returns true if the payload is valid; otherwise, it throws an InvalidPayloadException detailing the issue.
Tests
To run tests:
License
This software is published under the MIT License.
