PeX

Introduction

Caixabankpc, PeX from now on, is a form of financing for e-commerce facilitated by CaixaBank Payments & Consumer (CPC). Allows your customers to split purchases from 60€ to 1000€, both amounts included.

This payment method is available to customers with spanish nationality (DNI or TIE) and with Euro currency. On the payment request, a redirection will be made to the CPC website where the client will fill in a form with the necessary data to complete the operation, and the first payment of the loan will also be made. 

If you want to offer this payment method on your e-commerce with Addon Payments, certain requirements must be met. 

The merchant requirements are the signing of a contract between your merchant and CaixaBank Payments & Consumer (CPC). This will create a profile for your merchant on their platform.

Payment typeFinancing
Countries availableSpain
Currencies availableEuro
Minimum payment amount€60
Maximum payment amount€1.000
Redirection required?Yes
Two-step payment allowed?No
Refunds allowed?No
  1. You can obtain contact information as well as more information about the contracting process at this link.
  2. Details about minimum and maximum amounts, conditions, fees, interest rates, etc., can be obtained from your CPC agent. Addon Payments Support does not have access to these details.
  3. We recommend you to inform your CPC agent that the registration of your business is for payment processing by Addon Payments. 
  4. When CPC finalizes the registration of your merchant in its network, it will provide the necessary data for the activation of PeX to Addon Payments, and from Support we will proceed to its configuration and activation.

The customer requirements are:

  • Have an active credit card in a Euro currency issued by CaixaBank. 

Finally, you have a Postman collection where you can test the different PeX operations:

Operations supported

PeX is available on the Host2Host integration. Check the documentation to know more. The supported operations are:

  • Authorization: A regular payment from the customer to your merchant. The capture of the amount is automatic.
  • Void/cancellation: Cancellation of the financing amount. Only via endpoint. 

Also, PeX has supported amounts, currencies and countries. So this payment solution can only be used taking this into account:

  • Minimum and maximum amounts: 60€ and 1000€. Both included. These amounts will depend on the agreed conditions between your business and CPC.
  • Countries: Spain.
  • Currency: Euro.

Test cards

These are the cards that you can use to test PeX on the Staging environment. The result will depend on the test card used:

PAN3DS authenticationResult
4907270002222227FrictionlessAuthorized
4012000000020014AttemptAuthorized
4012000000150084ChallengeAuthorized
4012000000160083Declined
4012000000000081Indefined
4012000000010080Not authenticated
4907271141151707Declined (Error 190)
4907271141151708Declined (Error 195)
4907271141151709Declined (Error 180)

Environments and endpoints: Staging and Production

Addon Payments has two (2) independent operating environments:

Staging environment:

  • It is the first environment with which you will come into contact.
  • You can test with the credentials from the previous section.
  • This allows you to check the correct management of the different cases by your integration.
  • Real cards and accounts don’t work.

Production Environment:

  • It is the environment in which transactions have accounting effects.
  • Transactions can only be made with real and operative cards and accounts.

Below are the endpoints for Host2Host requests:

EnvironmentURL
Staginghttps://checkout-stg.addonpayments.com/EPGCheckout/rest/online/pay
Productionhttps://checkout.addonpayments.com/EPGCheckout/rest/online/pay

PeX integration

With Addon Payments, you can integrate the PeX payment solution on your Host2Host integration. However, you must do some modifications: 

  1. Manage the “AWAITING_PAYSOL” status of transactions pending customer completion of the data entry process and acceptance of terms and conditions. 

PeX required and optional data

These are the required/mandatory (R) and optional (O) parameters to perform a PeX request via Host2Host. The optional fields, while are not mandatory, allow that some fields on the CPC form appear filled in.

FieldFormatTypeDescriptionExample
merchantIdWhole number
4~7 digits		RYour merchant’s ID on the AP platform. Provided by Support in the welcome email. It is the same for both environments14983
merchantTransactionIdAlphanumeric
Max 12 characters
Min 4 characters		RThis is the unique identifier of the merchant’s transaction. It is used by your platform to link the notifications received with the customer’s order.pedido_91684
amountNumerical with decimals
Min 60 Max 1000		RAmount of the transaction. If the amount has decimals, the separator is a dot (.). The separator cannot be included in the thousands.127.5
currencyAlphabetical
3 characters
ISO-4217.3		RCurrency of the transaction. Limited to euro.EUR
countryAlphabetical
2 characters
ISO 3166-1 alfa-2		RCountry from which the transaction is sent. Limited to Spain (ES).ES
customerIdAlphanumeric
Max 80 characters		RCustomer ID in your e-commerce platform.A34623
paymentSolutionAlphanumeric
Max 45 characters		RName of the payment solution to process the transaction. In this case, PeX (caixabankpc).caixabankpc
firstNameAlphabetical
Max 30 characters		RCustomer’s name. If more than one, use spaces between them.
Must match the name of the cardholder. (chName).		Pablo
lastNameAlphabetical
Max 30 characters for surname (max 2 surname)		RCustomer’s surname(s)
Both surnames must be sent, with a space between them.
Must match the name of the cardholder. (chName).		Ferrer López
customerNationalIdAlphanumeric
9 characters		RDNI (with letter) for Spanish customers.
For foreigners, is the TIE number.		99999999R
customerEmailAlphabetical
Max 100 characters		RCustomer’s email address.correo@mail.com
telephoneNumerical 9 characters. Spanish number.RCustomer phone number. Must be a spanish phone number, no country code.600600600
statusURLAlphanumeric (characters allowed in URL)
Max. 2048 characters		RURL of your e-commerce platform where AP will send the notification with the status of the transaction. If it is sent in the request, it will take priority over the one configured in the Addon Payments BackOffice Portal. If it is not sent in the request, the customer will be redirected to the URL configured in the administration module.https://www.example.com/status
successURLAlphanumeric (characters allowed in URL)
Max. 2048 characters		RURL of your platform to which the customer is redirected if the transaction is authorized. If it is sent in the request, it will take priority over the one configured in the Addon Payments BackOffice Portal. If it is not sent in the request, the customer will be redirected to the URL configured in the administration module.https://www.example.com/success
errorURLAlphanumeric (characters allowed in URL)
Max. 2048 characters		RURL of your platform to which the customer is redirected if the transaction is declined. If it is sent in the request, it will take priority over the one configured in the Addon Payments BackOffice Portal. If it is not sent in the request, the customer will be redirected to the URL configured in the administration module.https://www.example.com/error
cancelURLAlphanumeric (characters allowed in URL)
Max. 2048 characters		RURL of your platform to which the customer is redirected if the transaction is cancelled during the payment process. If it is sent in the request, it will take priority over the one configured in the Addon Payments BackOffice Portal. If it is not sent in the request, the customer will be redirected to the URL configured in the administration module.https://www.example.com/cancel
awaitingURLAlphanumeric (characters allowed in URL)
Max. 2048 characters		RURL of your platform to which the customer is redirected if the transaction is pending processing. If it is sent in the request, it will take priority over the one configured in the Addon Payments BackOffice Portal. If it is not sent in the request, the customer will be redirected to the URL configured in the administration module.https://www.example.com/awaiting
addressLine1Alphanumeric
Max 50 characters		OFirst line of the customer address.Calle canales 2
addressLine2Alphanumeric
Max 20 characters		OSecond line of the customer address. 3 F
cityAlphabetic
Max 25 characters		OCustomer’s cityBarcelona
postCodeAlphanumeric
Max 5 characters		OCustomer’s postal code08003
financialInfoObject.
JSON of maximum 3000 characters.
Must contain:
– indCesionDatos
And may contain:
– indKYC
– descProductosCesta		RField containing parameters in JSON format. JSON maximum 3000 characters.
*** In the drop down below you have an example. 		N/A
− indCesionDatosValues are:
– “S”
– “N”		RIndicator of data transfer, for sending and processing of personal data (name, surname…) from AP to CPC.
If “S” is sent, the customer’s request data will be used to automatically fill in the CPC page.
If “N” is sent, the customer will have to manually enter the data.
You can include the checkbox on your website or let the customer fill it in on the CPC page.
* In the dropdown below, you can see more information about legal texts. 		S
− indKYCValues are:
– “S”
– “N”		OCustomer Authorization Indicator to CPC to confirm identity with CaixaBank.
If accepted, CPC connects to CaixaBank, transmits and processes data to confirm identity.
If “S” is sent, the connection to confirm identity is accepted. If “N” is sent, no.
You can include a checkbox on your website or let the customer fill it in on the CPC page.
** In the dropdown below, you can see more information about legal texts.		S
− descProductosCestaObject.
JSON array.
May contain:
– name
– description
– code
– amount
– quantity		OField that can contain a description of the customer’s order with certain fields.
JSON array format (JSON containing multiple JSON, one per product, separated by commas). Note that the maximum size of “”financialInfo”” is 3000 characters. 		N/A
−− nameAlphanumericOName of the productProducto1
−− descriptionAlphanumericODescription of the productDescripción del producto 1
−− codeAlphanumericOCode of the productproductCode1
−− amountInteger numeric
Numeric format in CENTS, without punctuation marks. 		OTotal amount of all items in the product. Some points to keep in mind:
– It is the result of multiplying the price of the individual item by the number of items there are. For example, a product can have 3 items of 10€ each, so the amount would be 30€.
**** In the dropdown below you have an example. 		18000 // this is 180€
−− quantityInteger numericONumber of items of the product1

The customer must be able to choose whether to give their data with a checkbox on your website. If you do not include these checkboxes on your site and therefore do not send the parameters, the CPC platform will offer the customer the forms. That checkbox will affect whether “indCesionDatos” is “S” or “N”.

Contact your CPC agent to obtain the legal texts.

The customer must be able to choose whether to provide their data to confirm their identity on your website. If you do not include these checkboxes on your site and therefore do not send the parameters, the CPC platform will offer the customer the forms. A checkbox is recommended, which will control whether “indKYC” is “S” or “N”.

Contact your CPC agent to obtain the legal texts.

				
					“financialInfo”:
    “{
        "indCesionDatos":"S",
        "indKYC":"S",
        "descProductosCesta": "[
            {
                \"name\":\"producto1\",
                \"description\":\"Descripción producto1\",
                \"code\":\"CodProd1\",
                \"quantity\":\"3\",
                \"amount\":”30297\"
           }
    ]"
}”
				
			
				
					{
    [
        {
            "name": "Producto 1",
            "description": "Descripción producto 1",
            "code": "producto1",
            "amount": 5000, // Product amount: 50.00€ x 1 = 50.00 → 5000
            "quantity": 1
        },
        {
            "name": "Producto 2",
            "description": "Descripción producto 2",
            "code": "producto2",
            "amount": 10000, // Product amount: 50.00€ x 2 = 100.00 → 10000
            "quantity": 2
        }
    ]
}

Host2Host Integration

Authorization

Below is an example of the fields required to send PeX requests with your Host2Host integration from your e-commerce platform.

Request

This is an example of a PeX authorization request, the first as a string and the second as a cURL. Remember that the string must pass the encryption process. 

				
					merchantId=12345&merchantTransactionId=00000001&amount=302.97&currency=EUR&country=ES
&customerId=000001&paymentSolution=caixabanpc&statusURL=https://micomercio.com/recepcion_notificacion.php
&successURL=https://micomercio.com/url-ok.php&errorURL=https://micomercio.com/url-ko.php
&cancelURL=https://micomercio.com/url-cancelacion.php&awaitingURL=https://micomercio.com/url-espera.php
&financialInfo={"indCesionDatos":"S","indKYC":"S","descProductosCesta":"[{\"name\":\"producto1\",\"description\":\"Descripción producto1\",\"code\":\"CodProd1\",\"quantity\":\"3\",\"amount\":”30297\"}]"}
				
			
				
					curl --location --request POST 'https://checkout-stg.addonpayments.com/EPGCheckout/rest/online/pay' \
--header 'apiVersion: 5' \
--header 'encryptionMode: CBC' \
--header 'iv: mx3rdwlpuDA1vM14SFT5bw==' \
--form 'merchantId="12345"' \
--form 'encrypted="/kJtS1WhS33iGLIvOuv7ISPKF4D3lldTzKkEgeuuldajYz1f6xQrAj7RCJXYgaiLpTFzNe9VDkGEYMCF5CI6z2eZmPQBFMsVJtroV3mvgBhRdK6j64utR' \
--form 'integrityCheck="e55c1dae947b376645b8fbd7f3612f0cf63045236c80b643f8335d3c4050ec70"'

When you send the POST to Addon Payements, you will receive a notification with the PeX URL to which you must redirect the customer to complete the payment. When the customer accesses the PeX URL, you will receive a notification with the status AWAITING_PAYSOL, pending for the customer to complete the process.

				
					<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<response operation-size="1">
    <message>WorkFlow has finished successfully, for transaction Id: 7981301</message>
    <operations>
        <operation sorted-order="1">
            <amount>302.97</amount>
            <currency>EUR</currency>
            <details>{"altaCaptacion":{"captacion":{"impCompra":302.97,"impCuota":0.0,"impPrimeraCuota":0.0,"impUltimaCuota":0.0,"fechaUltimaModificacion","dateCreated":"Jun 10, 2024 9:58:23 AM","dateModified":"Jun 10, 2024 9:58:23 AM"}</details>
            <merchantTransactionId>DocPEX003</merchantTransactionId>
            <message>Customer redirected to finish the process.</message>
            <operationType>DEBIT</operationType>
            <optionalTransactionParams/>
            <paymentDetails>
            <extraDetails/>
            </paymentDetails>
            <paymentSolution>caixabankpc</paymentSolution>
            <redirectionResponse>redirect:https://finonlinepre.caixabankconsumer.com/v3/#/Nombre_Comercio/reentrada/CDCE2C04447A1D545634BFFD24EF7D403E02BD92E7A7954DB2053CCA6DF8E103</redirectionResponse>
            <status>REDIRECTED</status>
            <transactionId>7981301</transactionId>
            <respCode>
                <code>0000</code>
                <message>Successful</message>
                <uuid>8435ae2b_8592_4c59_b03d_4d7bf537f3c3</uuid>
            </respCode>
        </operation>
    </operations>
    <optionalTransactionParams/>
    <status>SUCCESS</status>
    <workFlowResponse>
        <id>30285</id>
        <name>Debit</name>
        <version>40</version>
    </workFlowResponse>
</response>
				
			
				
					<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <response operation-size="1">
        <message>WorkFlow has finished successfully, for transaction Id: 7981301</message>
        <operations>
            <operation sorted-order="1">
                <amount>302.97</amount>
                <currency>EUR</currency>
                <merchantTransactionId>DocPEX003</merchantTransactionId>
                <message>Pre-authorized request</message>
                <operationType>DEBIT</operationType>
                <paySolTransactionId>202302580369467</paySolTransactionId>
                <paymentSolution>caixabankpc</paymentSolution>
                <status>AWAITING_PAYSOL</status>
                <transactionId>7981301</transactionId>
                <respCode>
                    <code>0000</code>
                    <message>Successful</message>
                    <uuid>480f09bc_fa1b_49e0_857a_e06ee847af96</uuid>
                </respCode>
            </operation>
        </operations>
        <optionalTransactionParams/>
        <status>SUCCESS</status>
    </response>

Authorization request parameters

The required/mandatory (R) and optional (O) parameters to perform a PeX request via Host2Host are in this table.

Response

This is an example of the final notification you receive informing you of the status of the PeX transaction:

				
					<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <response operation-size="1">
        <message>WorkFlow has finished successfully, for transaction Id: 7981382</message>
        <operations>
            <operation sorted-order="1">
                <amount>302.97</amount>
                <currency>EUR</currency>
                <merchantTransactionId>DocPEX006</merchantTransactionId>
                <message>Formalized request</message>
                <operationType>DEBIT</operationType>
                <paySolTransactionId>202302580369467</paySolTransactionId>
                <paymentSolution>caixabankpc</paymentSolution>
                <status>SUCCESS</status>
                <transactionId>7981382</transactionId>
                <respCode>
                    <code>0000</code>
                    <message>Successful</message>
                    <uuid>808a4821_ec99_4677_b8a9_adffb4789003</uuid>
                </respCode>
            </operation>
        </operations>
        <optionalTransactionParams/>
        <status>SUCCESS</status>
    </response>

Cancellation

Addon Payments allows cancellations of financing requests that are in process, with status “AWAITING_PAYSOL”. If the transaction is in a final status, like “SUCCESS” or “ERROR”, it can’t be cancelled. 

These are the endpoints where you must send the cancellation request:

EnvironmentURL
Staginghttps://checkout-stg.addonpayments.com/EPGCheckout/rest/online/cancel
Productionhttps://checkout.addonpayments.com/EPGCheckout/rest/online/cancel

Request

This is an example of a request to cancel a PeX financing operation with status “AWAITING_PAYSOL”. Remember that the string request must pass the encryption process.

				
					merchantId=12345&merchantTransactionId=00000001&transactionId=7981634&amount=302.97&currency=EUR
&country=ES&paymentSolution=caixabanpc&merchantParams=codMotivoCancelacion:01
;comentarios:El cliente ha cancelado el pedido
				
			
				
					curl --location --request POST 'https://checkout-stg.addonpayments.com/EPGCheckout/rest/online/cancel' \
--header 'apiVersion: 5' \
--header 'encryptionMode: CBC' \
--header 'iv: mx3rdwlpuDA1vM14SFT5bw==' \
--form 'merchantId="12345"' \
--form 'encrypted="/kJtS1z1f6xQrAj7RCJXYgaiLpTFzNe9VDkGEYMCF5CI6z2eZmPQBFMsVJtroV3mvgBhRdK6j64utR' \
--form 'integrityCheck="e55c1dae947b376645b8fbd7f3612f0cf63045236c80b643f8335d3c4050ec70"'

Cancellation request parameters

These are the required/mandatory (R) parameters for a cancellation PeX request:

FieldFormatTypeDescriptionExample
merchantIdWhole number
4~7 digits		RYour merchant’s ID on the AP platform. Provided by Support in the welcome email. It is the same for both environments14983
transactionIdWhole number
max 100 digits		RID for the original transaction the cancellation applies to. Is received in the notifications.76543210
paymentSolutionAlphanumeric
max 45 characters		RName of the payment solution that processed the original transaction. Given in the response for the original transaction.caixabankpc
merchantTransactionIdMax 45 characters
Page of Latin-1 codes (ISO-8859-1)		RThis is the transaction ID on your ecommerce platform.
Allows your platform to link notifications received to the customer’s order.
Each transaction must have a unique ID.		order_91684
amountNumerical with decimals
Min 60 Max 1000		RAmount of the original transaction. If the amount has decimals, the separator is a dot (.). The separator cannot be included in the thousands.127.5
currencyAlphabetical
3 characters
ISO-4217.3		RCurrency of the original transaction. EUR
countryAlphabetical
2 characters
ISO 3166-1 alfa-2		RCountry from which the original transaction is sent. ES
merchantParamsparam1:value1;param2:value2;…;paramN:valueN;RThis field must contain the data of the following rows with their respective values.“codMotivoCancelacion:01;comentarios:The customer has cancelled the order”
− codMotivoCancelacion01
02
03
04		RCode of the reason for cancellation. If the customer cancels:
– 01: Purchase cancelled
– 02: Other payment solution chosen
If cancelled by the merchant:
– 03: Merchandise reservation time exceeded.
– 04: Other reason		01
− comentariosAlfanuméricoRDescription of the reason for cancellation.The customer has cancelled the order.

Response

This is an example of a notification you receive to a PeX cancellation request:

				
					<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<response operation-size="1">
    <operations>
        <operation sorted-order="1">
            <amount>302.97</amount>
            <currency>EUR</currency>
            <details>{"cancelStatus":"00","dateCreated":"Jun 10, 2024 12:19:38 PM","dateModified":"Jun 10, 2024 12:19:38 PM"}</details>
            <merchantTransactionId>00000001</merchantTransactionId>
            <message>Payment cancelled successfully.</message>
            <operationType>CANCEL</operationType>
            <optionalTransactionParams/>
            <originalTransactionId>7981634</originalTransactionId>
            <paymentSolution>caixabankpc</paymentSolution>
            <status>SUCCESS</status>
            <transactionId>7981634</transactionId>
            <respCode>
                <code>0000</code>
                <message>Successful</message>
                <uuid>ddd7a05a_43b5_4055_94a8_3145292ff292</uuid>
            </respCode>
        </operation>
    </operations>
</response>

Error codes

These are the error codes that you may receive in PeX notifications. You can find them in the lines «code», «paymentCode», «paymentMessage».

< code > AP response codeAP message< paymentCode > Payment solution response code< paymentMessage > Payment solution message
1610A parameter on the payment call is invalid, check the Payment Solution ResponseVAL00002A field has no numerical value
1610A parameter on the payment call is invalid, check the Payment Solution ResponseVAL00006The telephone must start with 6, 7, 8 or 9
1610A parameter on the payment call is invalid, check the Payment Solution ResponseVAL00009A field has a length different than expected
1610A parameter on the payment call is invalid, check the Payment Solution ResponseVAL00011A field exceeds the max length
2000General communication errorProblems communicating to caixabankpc
3099Unidentified errorNot authorized request (NOAUT in caixabankpc)
5000Internal server errorUnexpected error on our side
5037There is a parameter in the request that is mandatoryMissing mandatory parameter
5498Non voidable transactionError cancelling the transaction

Customer experience

When the customer has chosen the product on your website that he wants to buy, and if the amount is between the minimum and maximum (60€ and 1000€), the customer can choose PeX as the payment method among those available on your website.

If you have included the data transfer forms (indCesionDatos and indKYC) on your website, the customer will be able to accept or reject with the corresponding checkbox. Afterwards, the customer will be redirected to a CPC URL where to continue the process.

On the CPC platform, the process to be followed will be different depending on the type of customer:

  • Known user: From CaixaBank or CPC. 
  • New user: Is not a customer of either.
  • Previous customer (Reuse): An user that has already used the service and has an open credit line. 

Below, you have a diagram with the steps that each client type must follow:

Comparte este documento
Tabla de Contenidos

Consulta la documentación de las distintas secciones de integraciones:

Comienza a integrar

undraw_add_to_cart_re_wrdo 1 (1) (1)

Plugins para CMS

Complementa la integración

SDKs

Métodos de pago

Herramientas

Addon Payments

Consulta la documentación de Addon Payments. Aquí tienes las distintas secciones:

Integraciones

Consultas frecuentes

Portal Backoffice

Cyberpac

We are currently working on the English version of the Cyberpac documentation. You can view the Spanish version using the buttons below:

Canales BackOffice Portal

Plugins integration

Custom integrations

POS integrated Payments

Create a solution that will help you automate processes. You can even add payment processes on physical terminals.

Payment Integrated with Android POS

Payment Integrated with Smartphone POS

POS Data sheets

Addon Payments

Comercia Global Payments has several integration options so you can choose the most efficient one for you.

Integrations

Frequently Asked Questions

BackOffice Portal

Consult the documentation of the different integrations sections:​

Start integration

undraw_add_to_cart_re_wrdo 1 (1) (1)

CMS Plugins

Complement your integration

SDKs

Payment Methods

Tools