Download the PHP package eonx-com/payments-phpsdk without Composer
On this page you can find all versions of the php package eonx-com/payments-phpsdk. 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 payments-phpsdk
EoneoPay PHP SDK
Transactions
The status of the transaction can be determined using the state property. There are situations where a transaction can be approved or completed but reversed at a later time. The state property is the only way to determine the actual state of the transaction. A table listing the meaning of each of the state field values is below.
| Value | State | Description |
|---|---|---|
| 1 | Pending | Request received, pending processing |
| 2 | Processing | Request is being processed |
| 10 | Provisionally approved | May be reversed, but funds could be available after clearing |
| 11 | Approved | Funds will be available after clearing |
| 90 | Failed/reversed/declined | Funds could not be transferred, and are not available |
| 80 | Finalised/cleared | Funds have transferred to destination are available |
Development
Main repository: https://github.com/loyaltycorp/eoneopay-phpsdk
Adding Entities
Entities are the class types the SDK exposes for serialising before sending to payments in JSON form, and the class type the responses are de-serialised to on response.
Entities are in the src/Endpoints directory, under the EoneoPay\PhpSdk\Endpoints namespace.
URIS
URIs list the acceptable actions that can be performed against with a given entity. These can be accessed
programmatically by calling the uris() method on an entity instance.
Entity Serialisation / @Groups
The @Groups annotation indicates the which fields which will be serialised before being sent as JSON. The
annotation uses Symfony\Component\Serializer\Annotation\Groups.
In the following example, the $actionUrl would be serialised when being sent to payments for both create and
update calls, but $amount will only be sent for the initial create call.
The @Groups annotations can be used on the same fields as @Assert annotations below.
Entity Deserialisation / Validation
Validation is applied to the JSON responses from payments to ensure that the returning fields are valid.
In the following examples, $id must be a string, which can't be null. $ewallet must be de-serialisble to a a valid
object of the type Ewallet.
Note that the @var annotation is used to discover the entity type that the contents of $ewallet should be
de-serialised to.
All versions of payments-phpsdk with dependencies
eonx-com/sdkblueprint Version ^1.0
eonx-com/utils Version ^1.0
ext-json Version *
symfony/validator Version ^4.2