API – Developers Docs API – Developers Docs
  • Cyberpac
  • Addon Payments
  • POS integrated Payments
  • SpanishSwitch to Spanish
API – Developers Docs API – Developers Docs
API – Developers Docs
  • Cyberpac
  • Addon Payments
  • POS integrated Payments
  • SpanishSwitch to Spanish
Addon Payments
  • Folder icon closed Folder open iconIntegrations
    • Start integrating
      • Welcome for CMS integrations
      • Introduction to integrations: Hosted, Host2Host and JavaScript
    • CMS Plugins
      • Prestashop
        • PrestaShop installation and set-up
        • Common mistakes with PrestaShop installation and set-up
        • Managing transactions with PrestaShop
      • WooCommerce
        • WooCommerce installation and set-up
        • Common mistakes with WooCommerce installation and set-up
        • Managing transactions with WooCommerce
      • Magento
        • Magento installation and set-up
        • Common mistakes with Magento installation and set-up
        • Managing transactions with Magento
      • Salesforce
        • Salesforce Commerce Cloud
    • Cards
      • Hosted Integration
      • Host2Host Integration
      • JavaScript Integration
      • PSD2 and 3DSv2
      • PCI DSS Certification
    • Complement your integration
      • Additional features
      • Managing notifications
      • Complement your JavaScript integration
      • Customizing the payment experience
      • Going Live (Switching to Production)
      • Encryption, signature and sending the request
      • Redirecting customer
    • Payment methods
      • Apple Pay
      • PayByBank
      • Bizum
      • PeX
      • Quix
    • Resources
      • Glossary
      • Payment solutions
      • Response codes
      • State and country codes
      • Currency codes
      • ID document type codes and validations
      • Test cards
    • Tools
      • Postman
      • SDKs
  • Folder icon closed Folder open iconBackOffice Portal
    • Pay by link guide
    • Search operations
    • Creating users
  • Folder icon closed Folder open iconFrequently Asked Questions

Test cards

Introduction

The cards on this list allow you to simulate the following actions in a staging environment:

  • Different operations.
  • Types of authentication, such as frictionless or challenge.
  • Results, such as authorized or declined.

The cards belong to the Addon Payments Merchant Plug-In (MPI). If you’re not sure which MPI your merchant uses, we recommend you test with the Addon Payments MPI cards, as it is the one set up by default.

    Test cards

    These are the credentials for the test cards:

    Expiry: Any date is valid.

    CVV2: Any CVV.

    • 3 digits for Visa and Mastercard.
    • 4 digits for AmEx.
    BRANDPANCURRENCY3DS VERSIONAUTHENTICATIONAUTHORIZATION
    Visa4907270002222227Euro2.2.0Frictionless*Authorized
    Visa4012000000020014Euro2.2.0Attempt**Authorized
    Visa4012000000150084Euro2.2.0Challenge***Authorized
    Visa4907271141151707Euro2.2.0FrictionlessDeclined 190 (rejected by issuer)
    Visa4907271141151715Euro2.2.0ChallengeDeclined 195 (soft decline)
    Visa4907271141151723Euro2.2.0FrictionlessDeclined 180 (card not supported)
    Visa4012000000010080Euro2.2.0Authentication error (wrong authentication)–
    Visa4012000000160083Euro2.2.0Authentication error (cancelled by customer)–
    Visa4012000000000081Euro2.2.0Authentication error (technical issues)–
    Visa4075131234567894Swedish Krona (SEK)2.2.0FrictionlessDCC EuroZone
    Visa4012000000061026United States Dollar2.2.0ChallengeDCC

    Colour codes

    Green: Operation authorized.
    Red: Operation declined.
    Yellow: Authentication error.

    *Frictionless

    A Frictionless authentication is a transparent verification method without interruptions in which the cardholder doesn’t have to take any additional actions during the transaction.

    **Attempt

    An Attempt authentication refers to an attempt to verify the user’s identity using an authentication process, which may include various security measures and methods.

    ***Challenge

    A challenge authentication is a verification process that requires active participation from the cardholder, generally having them input a code or answer a security question.

    Testing ecommerce with the Comercia 3DS server

    There are two main 3DS servers connected to Addon Payments and your merchant may be connected to either of these two 3Ds servers.

    By default, which is highly recommended, merchants normally use the Comercia 3DS server (also known as Comercia MPI). If this is your case, go to the Ecommerce Tests – Comercia 3DS Server page.

    Please contact the Support team if you have any questions about which 3DS server you are using.

    Test Cards and Random Data

    For the use cases below, you can make a payment with the following information.

    TRA

    Send a value in the lastName field that contains these values:

    • TRA: The Transaction Risk Analysis approves the request for 3DS exemption.
    • block: The Transaction Risk Analysis rejects and blocks payment.
    • continue: The Transaction Risk Analysis transfers the payment to 3DS.
    • force: The Transaction Risk Analysis transfers the payment to 3DS, forcing the 3DS challenge.
    				
    					lastName=force
    				
    			

    Remember, you also have to send the field “merchantExemptionsSca”. Otherwise the Transaction Risk Analysis (TRA) won’t be executed and the transaction will go to 3DS.

    				
    					merchantExemptionsSca=TRA
    				
    			

    Authorization and 3DS

    Sending one of these values in the field “cardNumber”.

    Testing ecommerce with the Redsys 3DS server

    There are two main 3DS servers connected to Addon Payments and your merchant may be connected to either of these two 3Ds servers.

    By default, which is highly recommended, merchants normally use the Comercia 3DS server (also known as Comercia MPI). If this is your case, go to the Ecommerce Tests – Comercia 3DS Server page.

    Please contact the Support team if you have any questions about which 3DS server you are using.

    Test Information

    For the use cases mentioned previously, you can make payment with the following information.

    You can change any of the values.

    ParameterValueNotes
    countryES
    languageES
    merchantIdxxxxxProvided by AddonPayments
    APIVersion5
    customerEmailcustomer_email@addonpayments.email
    merchantTransactionIdid_unique_1234Unique value for each request
    addressLine1c/Calle 1
    addressLine2Edificio 2
    productIdxxxxxProvided by AddonPayments
    telephone655956956
    firstNameaddon payments
    lastName3dSettle
    paymentSolutioncreditcards
    dob1988-11-24
    operationTypedebit
    cityMadrid
    descriptionTest transaction
    customerIdxxxxxCustomer ID from merchant
    currencyEUR
    amount12.34
    checkoutTitlePayment page
    topLogohttps://styles.easypaymentgateway.com/images/epg_logo.jpg
    bottomLogohttps://styles.easypaymentgateway.com/images/epg_logo_white.png
    fontFamilyarial
    subTitleSubtitle page
    fontSize10
    statusURLhttp://api-developer-stg.easypaymentgateway.com:443/webhookinbox/in/epg/stat/ww
    successURLhttp://api-developer-stg.easypaymentgateway.com:443/finalRedirectionPage/success
    awaitingURLhttp://api-developer-stg.easypaymentgateway.com:443/finalRedirectionPage/success
    errorURLhttp://api-developer-stg.easypaymentgateway.com:443/finalRedirectionPage/success
    cancelURLhttp://api-developer-stg.easypaymentgateway.com:443/finalRedirectionPage/success

    Sample raw parameter request

    				
    					  
      country=ES&language=ES&merchantId=10310&APIVersion=5&customerEmail=customer_email@addonpayments.email&merchantTransactionId=TEST-REDSYS-03-05-90002&addressLine1=c/Olvera 1&addressLine2=Olvera&productId=103100003&telephone=956956956&firstName=bbva&paymentSolution=creditcards&dob=1988-11-24&operationType=debit&lastName=3dSettle&city=Olvera&description=jesús&customerId=testRedsysPuce&currency=EUR&amount=10&checkoutTitle=Checkout Page&topLogo=https://styles.easypaymentgateway.com/images/epg_logo.jpg&bottomLogo=https://styles.easypaymentgateway.com/images/epg_logo_white.png&fontFamily=arial&subTitle=This is the sub title page&fontSize=10&statusURL=http://api-developer-stg.easypaymentgateway.com:443/webhookinbox/in/epg/stat/ww&successURL=http://api-developer-stg.easypaymentgateway.com:443/finalRedirectionPage/success&awaitingURL=http://api-developer-stg.easypaymentgateway.com:443/finalRedirectionPage/success&errorURL=http://api-developer-stg.easypaymentgateway.com:443/finalRedirectionPage/success&cancelURL=http://api-developer-stg.easypaymentgateway.com:443/finalRedirectionPage/succes
    				
    			

    Payment with 3DSv2 Challenge

    1. Make a payment request form using the details above.
    2. Fill in the card form with these values:
      • Card number: “4918019199883839” or “4918010000000010”
      • Expiry date: 1225.
      • CVV: 123.
    3. Addon Payments processes the payment and redirects the customer to the 3DSv2 challenge page.
    4. The customer must choose one of the following sections.

    Authentication and authorization complete

    				
    					<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <payfrex-response operation-size="1">
      <message>WorkFlow has finished successfully, for transaction Id: 415184</message>
      <operations>
        <operation sorted-order="1">
          <amount>10.00</amount>
          <currency>EUR</currency>
          <details>{"resultCode":"00000","result ... dsAuthenticationMethod":"Challenge"}</details>
          <merchantTransactionId>TEST-REDSYS-03-05-90002</merchantTransactionId>
          <message>Success 'Settle' operation with status 'SUCCESS'</message>
          <operationType>DEBIT</operationType>
          <optionalTransactionParams>
            <entry>
              <key>matchingData</key>
              <value>000000000000000415184</value>
            </entry>
            <entry>
              <key>puceResponse</key>
              <value>2</value>
            </entry>
          </optionalTransactionParams>
          <payFrexTransactionId>415184</payFrexTransactionId>
          <paySolTransactionId>999008881 790190 094555 210408153259</paySolTransactionId>
          <paymentDetails>
            <cardHolderName>Epg Pete</cardHolderName>
            <cardNumber>541008****0005</cardNumber>
            <cardNumberToken>3074432228970005</cardNumberToken>
            <cardType>mastercard/credit</cardType>
            <expDate>1225</expDate>
            <extraDetails>
              <entry>
                <key>cardCategory</key>
                <value>Not Available</value>
              </entry>
              <entry>
                <key>rememberMe</key>
                <value>true</value>
              </entry>
            </extraDetails>
            <issuerBank>SERVIRED, SOCIEDAD ESPANOLA DE MEDIOS DE PAGO, S.A.</issuerBank>
            <issuerCountry>ES</issuerCountry>
          </paymentDetails>
          <paymentMethod>{"operation":"payin","paysolId":"21400"}</paymentMethod>
          <paymentSolution>bbvapucpuce</paymentSolution>
          <status>SUCCESS</status>
          <respCode>
            <code>0000</code>
            <message>Successful</message>
            <uuid>ad131cf0_31a4_4c79_8114_429dd3750f9d</uuid>
          </respCode>
        </operation>
      </operations>
      <optionalTransactionParams/>
      <status>SUCCESS</status>
      <workFlowResponse>
        <id>4384</id>
        <name>BBVAPucPuce7</name>
        <version>20</version>
      </workFlowResponse>
    </payfrex-response>
    				
    			

    Authentication declined

    				
    					
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <payfrex-response operation-size="1">
      <message>WorkFlow has finished successfully, for transaction Id: 415186</message>
      <operations>
        <operation sorted-order="1">
          <amount>10.00</amount>
          <currency>EUR</currency>
          <merchantTransactionId>TEST-REDSYS-03-05-90003</merchantTransactionId>
          <message>Error en autenticación 3DSecure por parte del titular de la tarjeta</message>
          <operationType>DEBIT</operationType>
          <payFrexTransactionId>415186</payFrexTransactionId>
          <paymentMethod>{"operation":"payin","paysolId":"21400"}</paymentMethod>
          <paymentSolution>bbvapucpuce</paymentSolution>
          <status>ERROR</status>
          <respCode>
            <code>8032</code>
            <message>Authentication error</message>
            <uuid>dbe92194_195f_4436_9de9_d73215b224bf</uuid>
          </respCode>
          <paymentCode>184</paymentCode>
          <paymentMessage>Error en autenticación 3DSecure por parte del titular de la tarjeta</paymentMessage>
        </operation>
      </operations>
      <optionalTransactionParams/>
      <status>SUCCESS</status>
      <workFlowResponse>
        <id>4384</id>
        <name>BBVAPucPuce7</name>
        <version>20</version>
      </workFlowResponse>
    </payfrex-response>
    				
    			

    Authentication cancelled by cardholder

    				
    					
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <payfrex-response operation-size="1">
      <message>WorkFlow has finished successfully, for transaction Id: 415188</message>
      <operations>
        <operation sorted-order="1">
          <amount>10.00</amount>
          <currency>EUR</currency>
          <merchantTransactionId>TEST-REDSYS-03-05-90005</merchantTransactionId>
          <message>Error en autenticación 3DSecure por parte del titular de la tarjeta</message>
          <operationType>DEBIT</operationType>
          <payFrexTransactionId>415188</payFrexTransactionId>
          <paymentMethod>{"operation":"payin","paysolId":"21400"}</paymentMethod>
          <paymentSolution>bbvapucpuce</paymentSolution>
          <status>ERROR</status>
          <respCode>
            <code>8032</code>
            <message>Authentication error</message>
            <uuid>e1194109_f2e1_4b5f_b093_80aaad1a9de0</uuid>
          </respCode>
          <paymentCode>184</paymentCode>
          <paymentMessage>Error en autenticación 3DSecure por parte del titular de la tarjeta</paymentMessage>
        </operation>
      </operations>
      <optionalTransactionParams/>
      <status>SUCCESS</status>
      <workFlowResponse>
        <id>4384</id>
        <name>BBVAPucPuce7</name>
        <version>20</version>
      </workFlowResponse>
    </payfrex-response>
    				
    			

    Payment with Frictionless 3DSv2

    1. Make a payment request form using the details above.
    2. Fill in the card form with these values:
      • Card number: “4918010000000028” or “4918019160034602”
      • Expiry date: 1225.
      • CVV: 123.
    3. Addon Payments processes the payment and redirects the customer to the 3DSv2 challenge page.
    4. The customer must choose one of the following sections.

    Authorization complete

    Authorization declined

    				
    					
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <payfrex-response operation-size="1">
      <message>WorkFlow has finished successfully, for transaction Id: 415190</message>
      <operations>
        <operation sorted-order="1">
          <amount>10.00</amount>
          <currency>EUR</currency>
          <details>{"resultCode":"21190","resultDescription":"Denied for some reasons.","values":{"OperationResult":"190"},"initEmv3dsResponse":"{"status":"SUCCESS","resultCode":"00000","resultDescription":"OK","order":"415190","transactionType":"H","cardPSD2":"Y","protocolVersion":"2.2.0","exceptions":"LWV;TRA[10.0];COR;MIT;ATD;WHL","threeDsMethodParameters":{"threeDSServerTransId":"229b5e09-960e-4b76-a795-d9968ee2beed","threeDSInfo":"CardConfiguration"}}","authEmv3dsResponse":"{"status":"SUCCESS","resultCode":"00000","resultDescription":"OK","responseCode":"0900","order":"415190","transactionType":"17","securePayment":"2","processedPayMethod":"80","merchantData":"000000000000000415190","authorisationCode":""}","validateEmv3dsResponse":"{"status":"SUCCESS","resultCode":"00000","resultDescription":"OK","responseCode":"0900","order":"415190","transactionType":"17","securePayment":"2","processedPayMethod":"80","merchantData":"000000000000000415190","authorisationCode":""}","threeDsProtocolVersion":"2.2.0","emv3dsAuthenticationMethod":"Frictionless"}</details>
          <merchantTransactionId>TEST-REDSYS-03-05-916</merchantTransactionId>
          <message>Denied 'Settle' operation with code: 190 message: Denegación del emisor sin especificar motivo</message>
          <operationType>DEBIT</operationType>
          <optionalTransactionParams>
            <entry>
              <key>matchingData</key>
              <value>000000000000000415190</value>
            </entry>
            <entry>
              <key>puceResponse</key>
              <value>2</value>
            </entry>
          </optionalTransactionParams>
          <payFrexTransactionId>415190</payFrexTransactionId>
          <paymentDetails>
            <cardHolderName>Epg Pete</cardHolderName>
            <extraDetails/>
          </paymentDetails>
          <paymentMethod>{"operation":"payin","paysolId":"21400"}</paymentMethod>
          <paymentSolution>bbvapucpuce</paymentSolution>
          <status>ERROR</status>
          <respCode>
            <code>1638</code>
            <message>Issuer declined the transaction, please check payment solution respond</message>
            <uuid>37d36220_3a4c_48fe_b0a8_b0a2f019cc67</uuid>
          </respCode>
          <paymentCode>190</paymentCode>
          <paymentMessage>Denegación del emisor sin especificar motivo</paymentMessage>
        </operation>
      </operations>
      <optionalTransactionParams/>
      <status>SUCCESS</status>
      <workFlowResponse>
        <id>4384</id>
        <name>BBVAPucPuce7</name>
        <version>20</version>
      </workFlowResponse>
    </payfrex-response>
    				
    			
    Comparte este documento

    Test cards

    Copiar el enlace

    Clipboard Icon
    Tabla de Contenidos

    Products

    • Cyberpac
    • Addon Payments
    • POS integrated Payments
    • Universal Pay

    Sales

    Tell us about your business so we can offer you the best solution.

    Contact an expert
    Contact an expert
    Contact an expert
    Contact an expert
    Contact an expert

    Technical Support

    Already a client and need help? Contact us, we’re here for you.

    Help

    Partners

    We work with the best partners for in-store and ecommerce solutions. Want to join us?

    Join us

    © Comercia Global Payments

    Privacy policy
    Exercising rights
    Client information
    Whistleblowing channel
    Legal disclaimer
    Cookies policy
    Ask AI
    Write your question. For example: How do I create a payment link?
    SmartWiki may skip data. Verify the information or contact support.

    SmartWiki, Powered by AI

    API - Developers Docs
    Manage cookie consent

    To offer the best experiences, we use technologies such as cookies to store and/or access device information. Consent to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Failure to consent, or withdrawal of consent, may adversely affect certain features and functions.

    Functional Always active
    Storage or technical access is strictly necessary for the legitimate purpose of allowing the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
    Preferences
    Technical storage or access is necessary for the legitimate purpose of storing preferences not requested by the subscriber or user.
    Statistics
    El almacenamiento o acceso técnico que es utilizado exclusivamente con fines estadísticos. Storage or technical access that is used exclusively for anonymous statistical purposes. Without a requirement, voluntary compliance by your Internet service provider, or additional records from a third party, information stored or retrieved solely for this purpose cannot be used to identify you.
    Marketing
    Storage or technical access is necessary to create user profiles to send advertising, or to track the user on a website or several websites for similar marketing purposes.
    Manage options Manage services Manage {vendor_count} vendors Read more about these purposes
    See preferences
    {title} {title} {title}

    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