Download the PHP package zjl606/moneris-api without Composer
On this page you can find all versions of the php package zjl606/moneris-api. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download zjl606/moneris-api
More information about zjl606/moneris-api
Files in zjl606/moneris-api
Package moneris-api
Short Description Moneris API 修改了craigpaul/moneris-api的代码
License MIT
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 moneris-api
Moneris API
Requirements
PHP 5.6 and later
Composer
To get started, install the package via the Composer package manager:
Instantiation
Creating a new Moneris instance is quite easy and straightforward.
Note: Please note that the Moneris store id and API token are always required to be passed to the Moneris constructor or static create method.
Transactions
To make a purchase, preauth a card, void a transaction, etc. is very straightforward once you have your Gateway instantiated (see above).
Purchase
Pre-Authorization
Capture (Pre-Authorization Completion)
Void (Purchase Correction)
Refund
Card Verification
CVD and AVS
To take advantage of the Card Verification Digits and/or Address Verification Service provided by Moneris, you need to tell Moneris that upon instantiation (as shown above).
When making a CVD secured purchase, pre-authorization or card verification, you need to pass the following parameter to the Gateway method you are utilizing.
When making an AVS secured purchase, pre-authorization or card verification, you need to pass the following parameters to the Gateway method you are utilizing.
Note: When making an AVS or CVD secured transaction, even if AVS or CVD fails, you will still have to void the transaction (DAMN MONERIS!). There are two easy ways around this.
Verify the card first. Using this method, there is one additional caveat (let me repeat it again...DAMN MONERIS!). Your verification transaction and purchase transaction must have different order_id parameters. One such solution could be to prepend an specific prefix to the front of verification order ids.
Void the transaction.
Credential On File
The credential on file is part of the new Visa requirements to pass the CVD/CVV2 data for transactions.
Vault
The Moneris Vault allows you create and maintain credit card profiles on the Moneris servers instead of your own. To access the Vault, you will need to have your instantiated Gateway (see above).
Add a Card
Note: The expiry passed into the credit card is in the format of YYMM as that is how Moneris accepts it.
Update a Card
In order to maintain your credit card profiles, Moneris will send back a unique key for the profile that will allow you to keep track in your own database. You can retrieve the key once you have received your Receipt (see more below)
Delete a Card
Attaching a Customer
In order to sync your customer information with the credit cards stored in the Vault, we can attach a basic Customer object to the CreditCard.
Add a Card
Update a Card and Customer
Tokenize a Previous Transaction
Used to create a credit card profile based on a previous transaction.
Peek Into The Vault
If you have the need to look up the masked credit card number you can peek into the Vault.
Retrieve Expiring Cards
This transaction can be performed no more then 2 times on any given calendar day as per the Moneris API.
Transactions
Credit cards stored in the Moneris Vault have a slightly different flow for purchasing and pre-authorization. Any of the other transactions work exactly the same as shown above.
Vault Purchase
Note: The Vault is used for the transaction here instead of the base Gateway object.
Vault Pre-Authorization
Responses and Receipts
The Response and Receipt objects allow you to understand how everything went with your API call. After a transaction returns from being processed the Response will get validated and return all the relevant information for you.
Response
The information available to you on the Response object is as follows:
Errors
Any errors that might occur during your transaction will be returned in the following format for you. It is returned in this format to allow you to handle any translation logic in your own app by utilizing the unique title and field keys in each error.
Status
The status will return a status code matching the appropriate error returned. See below for an example of the possible statuses returned.
Success
The successful property simply lets you know if your transaction has been processed successfully.
Receipt
The Receipt object is your record of any information relevant to your transaction you have submitted. To retrieve your receipt once you have a response see the following.
Depending on that type of transaction, you will have different items on your Receipt that you have available to read.
For a full list of possible readable receipt items, see below.
Change log
Please see CHANGELOG for more information on what has changed recently.
Contributing
Please see CONTRIBUTING for details.
Credits
- Craig Paul
- All Contributors
License
Moneris API is open-sourced software licensed under the MIT license.
