creating card token for testing integration with backend

[ihojmanb]

Is there a way to create card tokens from the backend? Currently, the card token is generated through the clientside SDK with mercadopago.fields.createCardToken(...). This is a bit painful when trying to test my backend, as I have to go all the way from filling in the payment form by hand, generate the token, and make a POST request to receive that token into my backend.

Is there a smart way to generate card tokens for testing purposes or how can I import the clientside SDK in my backend?

[icaldana]

Hello @ihojmanb! Let me try to understand your pain.

1. Are you using backend SDK?
2. What kind of tests are you creating? At the first glance it seems you're running E2E tests, and if yes, it does make sense to include both FE and BE in the process. On the other hand, if the tests are unitary or even manual, couldn't you mock the token and save it as one environment variable?

[ihojmanb]

Hi @icaldana! sorry for not being that specific. Here's how it goes:

1. I'm integrating with the Checkout API V2 via Core Methods. So whenever I need to make a payment, I do something like this:

var payment_data = {
  transaction_amount: Number(req.body.transactionAmount),
  token: req.body.token,
  description: req.body.description,
  installments: Number(req.body.installments),
  payment_method_id: req.body.paymentMethodId,
  issuer_id: req.body.issuer,
  payer: {
    email: req.body.email,
  }
};

mercadopago.payment.save(payment_data)

What's bothering me here is the token value, since I (think) have to generate a valid token for the available test cards.
2. I'm testing it manually first, then I'm going with unit/E2E tests. How can I mock a card token to be a valid one?

I think all comes down to: how can I generate a valid token for the test cards available without passing by the front end?

[icaldana]

Thank you for clarifying it 😄

Unfortunately, this is part of PCI standards, thus, this is the expected behavior for these tests E2E/manual for security reasons.

In a nutshell: in order to test your custom logic you could mock the token, but when testing the SDK-js integration, it is required to pass by the front-end.

[ihojmanb]

Do you have any advice on how to mock the token? I tried using one shown in the documentation, but received 'Card Token not found' error (code 2006)

thanks for your help Ismael! 😄

[icaldana]

Just clarifying the tokens are designed to be single-use, then mocking makes sense only when you don't need to actually call mercadopago.payment.save. You could store a token example as environment variable https://nodejs.dev/en/learn/how-to-read-environment-variables-from-nodejs/

[ihojmanb]

thanks, gonna check it out!