EasyPay uses Standard SOAP API. This discovery can be found at: https://easypay5.com/apicardprocR119
The Soap API schema is documented in two separate areas:
1) Classic Interface
2) Method Definitions
Terms relevant for EasyPay API:
[OperationContract]
api_AuthResponse Authenticate (string AcctCode, string Token);
In order to use the EasyPay API you will need to first understand the AUTHENTICATION method. In this method you will pass us TWO values:
The return object will contain your SESSION KEY. All of our API methods require you send a session key. This key will be honored for 25 hours as long as it is sent from the same IP address which was originally used for AUTHENTICATION. Sometimes it happens that your IP (as seen by EasyPay) can change during any given 24-hour period and in that case, you may receive an ERROR CODE 5050 from our API. If that happens you will simply run the AUTHENTICATE method once again to obtain a new Session key.
We recommend that you simply obtain a session key and continue to use that session key until you receive one of the following error codes:
When you AUTHENTICATE you will be returned two Boolean flags:
The workflow should be as follows:
It is important that unsuccessful authentication attempts be ABORTED and NOT retried. The EasyPay system will LOCK your IP out if you continue to send us unsuccessful authentication attempts ( 6 in a row ) . This can cause serious problems for your merchants if they are locked out. Since it will require someone in our support department to manually audit the lockout and determine if it is safe to remove the lock. The better approach is to simply STOP and NOTIFY the User that new EasyPay Credentials be applied to the product. Once the New credentials are applied and the AUTHENTICATE method is executed then Card processing can continue without the need to perform an additional step to UNLOCK the account.
Account Code: EP4799974 (9 ALPHA NUMERIC) (never changes)
Token: 1A4901153DEA4CF6A8BAB1999FA36C34 (32 HEX) (expires every 6 months)
SESSION KEY: F9F3C25C9A1247F2AD303030363541303030353230 (42 HEX) (expires every 25 hours)
EasyPay provides a web site which allows you to manage and create new tokens. You are free to create as many Tokens as you require for your credit card processing requirements. We recommend that you create a token for each individual processing location (IP address). As Stated previously, Each Token has a lifespan of 6 months. When you create a new token, this does not affect the Tokens that were previously generated. Every Token you generate will last for two-years. When you Log Into our Client Admin Portal you will be able to View your existing Tokens, Create New Tokens, and we also allow you to POST tokens to your web site. This provides a degree of automation to the renewal process. In any event , you must physically log in to the web site using 2 factor authentication to create or manage or POST Tokens to a web site.
The Soap API schema is documented in two separate areas:
1) Classic Interface
2) Method Definitions