Download the PHP package visualr/omnipay-tillpayments without Composer
On this page you can find all versions of the php package visualr/omnipay-tillpayments. 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 omnipay-tillpayments
Omnipay: Till Payments
Till Payments driver for the Omnipay PHP payment processing library
Omnipay is a framework agnostic, multi-gateway payment processing library for PHP 5.3+. This package implements eWAY support for Omnipay.
Till Payments was founded in 2012 with the primary focus of helping technology vendors and their customers streamline their payments acceptance and operations.
Installation
Omnipay is installed via Composer. To install, simply add it
to your composer.json file:
And run composer to update your dependencies:
$ curl -s http://getcomposer.org/installer | php
$ php composer.phar updateBasic Usage
For general usage instructions, please see the main Omnipay repository.
Initializing Gateway
Remember! You will have different API Key for different connectors
Purchase Transaction
This is called Debit on Till Documentation
| Required Fields | Notes |
|---|---|
merchantTransactionId |
Your unique transaction ID. If left blank, default one will be used |
amount |
Decimals separated by ., max. 3 decimals |
currency |
3 letter currency code |
You can also pass transactionToken on the payload if you receive a token using Till Payment's payment.js
For more information about the payload, refer to: Till Payment Documentation
For more information about the card data, refer to: Omnipay Credit Card Documentation
Authorize Transaction
This is called Preauthorize on Till Documentation
A Preauthorize reserves the payment amount on the customer's payment instrument.
Depending on the payment method you have up to 7 days until you must Capture the transaction before the authorization expires.
| Required Fields | Notes |
|---|---|
merchantTransactionId |
Your unique transaction ID. If left blank, default one will be used |
amount |
Decimals separated by ., max. 3 decimals |
currency |
3 letter currency code |
You can also pass transactionToken on the payload if you receive a token using Till Payment's payment.js
For more information about the payload, refer to: Till Payment Documentation
For more information about the card data, refer to: Omnipay Credit Card Documentation
Capture Transaction
A Capture completes the payment which was previously authorized with the Preauthorize method.
Depending on the payment method you can even capture only a partial amount of the authorized amount.
| Required Fields | Notes |
|---|---|
merchantTransactionId |
Your unique transaction ID. If left blank, default one will be used |
amount |
Decimals separated by ., max. 3 decimals |
currency |
3 letter currency code |
referenceUuid |
UUID / transaction reference of a preauthorize |
For more information about the payload, refer to: Till Payment Documentation
For more information about the card data, refer to: Omnipay Credit Card Documentation
Purchase Transaction
This is called Debit on Till Documentation
| Required Fields | Notes |
|---|---|
merchantTransactionId |
Your unique transaction ID. If left blank, default one will be used |
amount |
Decimals separated by ., max. 3 decimals |
currency |
3 letter currency code |
For more information about the payload, refer to: Till Payment Documentation
For more information about the card data, refer to: Omnipay Credit Card Documentation
Authorize Transaction
This is called Preauthorize on Till Documentation
A Preauthorize reserves the payment amount on the customer's payment instrument.
Depending on the payment method you have up to 7 days until you must Capture the transaction before the authorization expires.
| Required Fields | Notes |
|---|---|
merchantTransactionId |
Your unique transaction ID. If left blank, default one will be used |
amount |
Decimals separated by ., max. 3 decimals |
currency |
3 letter currency code |
For more information about the payload, refer to: Till Payment Documentation
For more information about the card data, refer to: Omnipay Credit Card Documentation
Capture Transaction
A Capture completes the payment which was previously authorized with the Preauthorize method.
Depending on the payment method you can even capture only a partial amount of the authorized amount.
| Required Fields | Notes |
|---|---|
merchantTransactionId |
Your unique transaction ID. If left blank, default one will be used |
amount |
Decimals separated by ., max. 3 decimals |
currency |
3 letter currency code |
referenceUuid |
UUID / transaction reference of a preauthorize |
For more information about the payload, refer to: Till Payment Documentation
Void Transaction
A Void cancels a previously performed authorization made with the Preauthorize method.
| Required Fields | Notes |
|---|---|
merchantTransactionId |
Your unique transaction ID. If left blank, default one will be used |
referenceUuid |
UUID / transaction reference of a preauthorize |
For more information about the payload, refer to: Till Payment Documentation
Create Card Transaction
This is called Register on Till Documentation
Registers a customer's payment instrument for future charges (Debits or Preauthorizations)
| Required Fields | Notes |
|---|---|
merchantTransactionId |
Your unique transaction ID. If left blank, default one will be used |
For more information about the payload, refer to: Till Payment Documentation
For more information about the card data, refer to: Omnipay Credit Card Documentation
Delete Card Transaction
This is called Deregister on Till Documentation
A Deregister deletes a previously registered payment instrument using Register.
| Required Fields | Notes |
|---|---|
merchantTransactionId |
Your unique transaction ID. If left blank, default one will be used |
referenceUuid |
UUID of a register, debit-with-register or preauthorize-with-register |
For more information about the payload, refer to: Till Payment Documentation
For more information about the card data, refer to: Omnipay Credit Card Documentation
Refund Transaction
A Refund reverses a payment which was previously performed with Debit or Capture.
Depending on the payment method you can even refund only a partial amount of the original transaction amou
| Required Fields | Notes |
|---|---|
merchantTransactionId |
Your unique transaction ID. If left blank, default one will be used |
amount |
Decimals separated by ., max. 3 decimals |
currency |
3 letter currency code |
referenceUuid |
UUID of a register, debit-with-register or preauthorize-with-register |
For more information about the payload, refer to: Till Payment Documentation
For more information about the card data, refer to: Omnipay Credit Card Documentation
Payout Transaction
Coming soon
Incremental Authorization
Coming soon
The Payment Responses
Successful Response
For a successful responses, a reference will normally be generated, which can be used to capture or refund the transaction at a later date. The following methods are always available:
If you are going to implement refund and void, you will need to always save the transaction reference since it is often used as referenceUuid.
Redirect Response
After processing a payment, the cart should check whether the response requires a redirect, and if so, redirect accordingly:
The customer isn't automatically forwarded on, because often the cart or developer will want to customize the redirect method (or if payment processing is happening inside an AJAX call they will want to return JS to the browser instead).
To display your own redirect page, simply call getRedirectUrl() on the response, then display it accordingly:
Error Response
You can test for a successful response by calling isSuccessful() on the response object. If there was an error communicating with the gateway, or your request was obviously invalid, an exception will be thrown. In general, if the gateway does not throw an exception, but returns an unsuccessful response, it is a message you should display to the customer. If an exception is thrown, it is either a bug in your code (missing required fields), or a communication error with the gateway.
The simplest way is to wrap the entire request in a try-catch block.
Advanced Usage
Using Customer instead of CreditCard
Coming soon
Schedule
Coming soon
Accepting Notification
Coming soon
Support
If you are having general issues with Omnipay, we suggest posting on Stack Overflow. Be sure to add the omnipay tag so it can be easily found.
If you want to keep up to date with release announcements, discuss ideas for the project, or ask more detailed questions, there is also a mailing list which you can subscribe to.
If you believe you have found a bug, please report it using the GitHub issue tracker, or better yet, fork the library and submit a pull request.
