Download the PHP package arm092/omnipay-ameriabank without Composer

On this page you can find all versions of the php package arm092/omnipay-ameriabank. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

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 PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • 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.
Please rate this library. Is it a good library?

Informations about the package omnipay-ameriabank

Omnipay: Ameriabank

Tests Latest Stable Version Total Downloads PHP Version License

Ameriabank VPOS gateway for Omnipay, compatible with PHP 7.4 and PHP 8.

Installation

Install the gateway; the Guzzle HTTP adapter is included as a dependency:

Register a payment and redirect

A successful InitPayment only registers an order. Its isSuccessful() is false; use isRedirect() to proceed. The redirect automatically inherits the request's test mode. setTestMode() on the response remains available for existing callers.

Verify payment after the browser returns

BackURL is a browser return URL, not a trusted server webhook. Do not mark an order paid based on the callback's resposneCode, orderID, or opaque values. Find the local order using its stored bank PaymentID and query the bank:

getTransactionReference() returns the bank PaymentID. getTransactionId() on a details response returns the merchant OrderID. GetPaymentDetails does not return PaymentID, so the response retains the ID from its request.

Capture, cancel and refund

Check each response's isSuccessful(), getCode() and getMessage(). For existing integrations, these follow-up requests still accept PaymentID through transactionId; transactionReference takes precedence when both are supplied.

authorize() registers through InitPayment just like purchase(). Preauthorization must be enabled/configured for the terminal by Ameriabank; this method alone does not switch a single-stage terminal into two-stage mode. After return, use completeAuthorize() and check isAuthorized() (ResponseCode=00, OrderStatus=1), then capture() to deposit the amount. Authorization is not completed payment, so isSuccessful() remains false until OrderStatus=2. The API exposes an optional integer paymentServiceType on InitPayment, but its values are not explained on the Help page. Pass it only according to your bank-issued integration settings; the gateway does not guess a value for preauthorization.

Card bindings

To register a card binding through the hosted payment form, add a stable card_holder_id to purchase() (InitPayment). Keep the same ID for subsequent binding operations.

The historical createCard() method calls MakeBindingPayment: it charges an existing binding, rather than simply creating a card. Supply card_holder_id, transactionId, amount, currency and description as above. Supply returnUrl when authentication can require returning through the browser; it remains optional for existing bindings that charge without an interactive redirect. If the response isRedirect(), perform its redirect to complete 3-D Secure; the gateway supplies a POST with PaReq and TermUrl from the bank. If supplied, MD is forwarded unchanged. Otherwise check isSuccessful(). Always query GetPaymentDetails after authentication before marking the local order paid.

setBindingUsername() configures the username for createCard(), getBindings(), enableCard() and disableCard(); if omitted, the normal username is used. Enable/disable requests require card_holder_id. getBindings()->send() exposes getCardBindings(). The spelling CardBindingFileds is intentional in the bank API.

Compatibility changes

Tests

Tests use an HTTP mock and never contact payment endpoints. The lock file resolves dependencies for PHP 7.4.33, the lowest supported PHP line; the same suite can run on PHP 8. Production credentials, bank-enabled terminal settings and real 3-D Secure flows still need validation in the bank sandbox before release.

Ameriabank API documentation


All versions of omnipay-ameriabank with dependencies

PHP Build Version
Package Version
Requires omnipay/common Version ^3
php-http/guzzle7-adapter Version ^1
ext-json Version *
php Version ^7.4|8.*
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package arm092/omnipay-ameriabank contains the following files

Loading the files please wait ...