Payment page images image
Below you can find sample graphics with credit card issuer logos (one of Elavon’s requirements is the visibility of payment card issuer logos). Card acceptance symbols should be used in accordance with the recommendations of the card organizations to which the symbols belong.
link Card acceptance marks
link 3D Secure marks
link Combined logos
Resources for developers code
link List of requirements
The list of requirements concerning the contents of the Merchant’s page, on which the card payments will be accessible.
The requirements are based upon the Merchant contract with Elavon:
link Issuer response codes
Rejection codes from banks (“issuer_response_code” parameter) with descriptions for clients in Polish, English and French in the SQL format.
Rejection codes in PL and EN are the only ones which are complete. In other languages, we support the most common codes, therefore we suggest preparing your app to display those in default languages (EN or PL).
Numeration with the “id” field is only for aesthetic reasons, and may change in the future.
Ruby on rails
https://github.com/espago/php-examples - a script with minimal connection to APIv3.0 initiating a payment (without 3D-Secure) and a script receiving a back request.
https://github.com/espago/espago-1.2.js-demo - example of an implementation of a form using Espago JS to create and receive a Card or CVV Token.
link Espago Terminals
Here you can find browser extensions for Espago Terminals purposes.
Chrome web store
link 3D-Secure status codes
3D-Secure 2 status codes from banks (“tds_status_reason” parameter) with descriptions for clients in English in the YAML and SQL formats.
Rejection codes in EN are the only ones which are complete. In other languages, we support the most common codes, therefore we suggest preparing your app to display those in default languages (EN or PL).
link API response error messages
List of messages returned in each rejected query, in each element of the