Download the PHP package payever/sdk-php without Composer

PHP SDK for payever plugin interactions - internal, not for public use

This repository contains the open source PHP SDK that allows you to access payever from your PHP app.

This library follows semantic versioning. Read more on semver.org.

Please note: this SDK is used within the payever plugins. It is NOT suitable for custom API integrations. If you would like to integrate with us via API, please visit https://docs.payever.org/shopsystems/api and follow the instructions and code examples provided there.

Troubleshooting

If you faced an issue you can contact us via official support channel - [email protected]

Requirements

• PHP 5.4.0 and later
• PHP cURL extension

Installation

You can use Composer or install manually

Composer

The preferred method is via composer. Follow the installation instructions if you do not already have composer installed.

Once composer is installed, execute the following command in your project root to install this library:

Manual Installation

Alternatively you can download the package entirety. The Releases page lists all stable versions.

Uncompress the zip file and invoke the autoloader in your project:

Documentation

Raw HTTP API docs can be found here - https://docs.payever.org/shopsystems/api

Enums

The are several list of fixed string values used inside API. For convenience they are represented as constants and grouped into classes.

• Core
  • ChannelSet - list of available payever API channels
• Payments
  • PaymentMethod - list of available payever payment methods
  • Status - list of available payever payment statuses
• ThirdParty
  • ActionEnum - list of available actions (webhooks)
  • DirectionEnum - list of available action directions
• Products
  • ProductTypeEnum - list of available payever product types
• Plugins
  • PluginCommandNameEnum - list of available plgin command types

API Clients

HTTP API communication with payever happens through API clients. There are several of them for different API categories:

• PaymentsApiClient
• ThirdPartyApiClient
• ProductsApiClient
• InventoryApiClient

Each one is described in details below.

Configuration

Each API client requires configuration object as the first argument of client's constructor. In order to get the valid configuration object you need to have valid API credentials:

• Client ID
• Client Secret
• Business UUID

Additionally, you need to tell which API channel you're using:

NOTE: All examples below assume you have ClientConfiguration instantiated inside $clientConfiguration variable.

Logging

You can setup logging of all API interactions by providing PSR-3 compatible logger instance.

In case if you don't have PSR-3 compatible logger at hand - this SKD contains simple file logger:

PaymentsApiClient

This API client is used in all payment-related interactions.

Create payment and obtain redirect url

Retrieve payment details by id

Cancel the payment by id

Trigger Santander shipping-goods payment action

ThirdPartyApiClient

This client can be used to initiate webhook-based data flow between your system and payever. As of now, only product and inventory webhooks are supported.

How it works:

• generate a unique string (externalId) to identify yourself inside payever system;
• create a data subscription with a list of webhooks you wish to consume;
• whenever specific event happens inside payever system you will receive an HTTP request to your webhook URL;

Subscribe

You can find the full list of available webhooks here.

Check subscription status

Useful when you need to check if your subscription is active or check the list of webhooks.

Unsubscribe

If you want to stop receiving webhook updates - you would need to call "unsubscribe" method.

Handling action (webhook) requests

Of course you can handle webhook requests manually, but there are several classes and interfaces for easier webhook handling.

You can define a class for each webhook type by implementing ActionHandlerInterface:

Once you created such handler classes for all webhooks, you can combine them into ActionHandlerPool and use InwardActionProcessor to handle all the routines for you:

ProductsApiClient

This client class is dependant on ThirdPartyApiClient and requires active third-party subscription with known externalId;

This API client can be used to create/update/delete (NOTE: "read" operation is not available atm) operations over payever products. Please note that products between any external system and payever are identified by SKU field.

Create or update product

Delete/remove product

InventoryApiClient

This client class is dependent on ThirdPartyApiClient and requires active third-party subscription with known externalId;

This API client can be used to create/add/subtract (NOTE: "read" operation is not available atm) operations over payever inventory. Please note that product inventory between any external system and payever are identified by SKU field.

Create product inventory record

"Create" operation can be done only once, all further "create" requests with the same SKU will be ignored. Use add/subtract operations to change the value of inventory once it created.

Add (increase) inventory value

Subtract (decrease) inventory value

License

Please see the license file for more information.