FAQ

1. Which cards can be used in the testing environment?

In the test environment, test cards should be used, preferably "false". Therefore we recommend the following:

1. For succesful transactions you can generate card numbers at https://www.getcreditcardnumbers.com/

2. To make transactions with some rejected code you must use the following:

Card number	Bank error code (proc_code)	Error message
4539790114303785	01	Refierase al emisor
4319593393858768	03	Comercio inválido
4556500081329277	04	Retirar tarjeta
4485970366452449	05	Denegada
4485684474633390	12	Transacción inválida
4024007189880601	13	Monto inválido trate de nuevo
4916402417466144	14	Tarjeta inválida
4539935161849723	19	Reingresar transacción
4345967438617249	31	Banco no soportado
4929639391534299	41	Tarjeta perdida
4716178359021988	43	Retener y llamar
4094394314664828	51	Fondos insuficientes
4539610492212483	54	Tarjeta vencida retire renovación
4556710706281072	55	Pin incorrecto
4556592228753727	58	Función no permitida
4929518506489375	262	Error al autorizar
4024007105223894	63	Error al autorizar
4716342493980323	65	Error al autorizar
4929597009464475	78	Error al autorizar
4539740270025870	89	Terminal inválido
4929942460623880	91	Emisor no contesta
4916869335186964	96	No soportada

2. What errors the chekout API returns?

Any transaction rejected either by our API, or the Bank will have a response status with code 500.

Checkout order creation service

Error message	Rejection reason
Bank entity doesn't exist	Terminal does not exist in our system
Merchant doesn't exist	MerchantId or secret does not exist in our system

Checkout service

Error code (proc_code)	Error message	Rejection reason
01	Refierase al emisor	Authorized bank rejected the transaction
03	Comercio inválido	Authorized bank rejected the transaction
04	Retirar tarjeta	Authorized bank rejected the transaction
05	Denegada	Authorized bank rejected the transaction
12	Transacción inválida	Authorized bank rejected the transaction
13	Monto inválido, trate de nuevo	Authorized bank rejected the transaction
14	Tarjeta inválida	Authorized bank rejected the transaction
19	Reingresar transacción	Authorized bank rejected the transaction
31	Banco no soportado	Authorized bank rejected the transaction
41	Tarjeta perdida	Authorized bank rejected the transaction
43	Retener y llamar	Authorized bank rejected the transaction
51	Fondos insuficientes	Authorized bank rejected the transaction
54	Tarjeta vencida, retire renovación	Authorized bank rejected the transaction
55	Pin incorrecto	Authorized bank rejected the transaction
58	Función no permitida	Authorized bank rejected the transaction
62,63,65,78	Error al autorizar	Authorized bank rejected the transaction
89	Terminal inválida	Authorized bank rejected the transaction
91	Emisor no contesta	Authorized bank rejected the transaction
296	No soportada	Authorized bank rejected the transaction
	Invalid_pan	Card number does not correspond to valid number
	Session not exists or is wrong	API cant decrypt the received data, a wrong card encryption process was executed
	Session not found	Value of the session parameter doesn't exist. -Already expired -Hasn't been created
	Invalid token	Liszt token does not match the one created in the process of creating the payment order. -Already expired -Hasn't been created
	Invalid input syntax for uuid	Some parameter values received dont match.

3- The card data encryption must be done in the fronEnd?

Yes, for security reasons the card data must be encrypted in the application frontEnd and the checkout should be invoked towards Greenpay from this application layer.

In addition, the card data should not travel in clear text to your own backend.

4- Should the payment order creation process be done in the backEnd?

It's recommended to do it in the backEnd, in order to avoid exposing the API credentials on the web.