Book a Demo

Mercado Pago - PSE

Suggest Edits

This page presents all information related to the Mercado Pago connection using the PSE as payment. Use the following buttons to navigate to the desired section.

General Information

Refunds

Chargebacks

Testing Guidelines

Integration Configuration

Production Environment

Connecting with Yuno

Mandatory fields when integrating via Yuno:

email
document_type
document_number
IP

General information

Countries:

colombia-flag
Colombia

Currencies:

COP

Minimum amount:

1600 COP

Maximum amount:

Defined by bank

TRX limit:

No, but it is important to inform the estimated volumes of a new integration in order to warn about the dimensioning to the tech teams, if necessary.

Purchase TRX:

Allows your customers to pay with PSE using the savings or checking account from any Colombian bank.

Purchase TRX in 2-Step:

No

Support for recurrency:

No

Webhooks:

Yes

Refunds

Refund support:

Yes

Partial sefunds:

Yes

Multiple refunds:

Yes

Time to request refund:

Within 180 days of its approval date.

Time to process refund:

10 - 13 working days.

Cancellation

Cancellation support:

Yes

Chargebacks

Notifications of chargebacks:

No

Testing guidelines for sandbox environment

Necessary fields for testing:

Public Key and Access Token

Requirements to create a sandbox payment:

To create a payment on the sandbox environment you need to use an email ending with @test.user.com, such as [email protected].

Integration configuration

Credentials and steps to obtain them:

They can be found on the Dashboard or in your Mercado Pago account by accessing Your Business > Settings > Management and Administration > Credentials.
Test credentials: Public Key, Access Token
Production credentials: Public Key, Access Token, Client ID, Client Secret

Configuration of webhooks in partner:

Via dashboard:
  1. Create an application on the homepage of your Dashboard.
  2. With the application created, go to the Webhooks Notifications tab in your Dashboard and configure the URLs of production and test from which notifications will be received.
  3. You will also be able to experiment and test if the indicated URL is receiving notifications correctly, being able to verify the request, the response given by the server and the description of the event.
  4. If you need to identify multiple accounts, at the end of the indicated URL you can indicate the parameter ?customer=(sellername) endpoint to identify the sellers.
  5. Next, select the events from which you will receive notifications in json format via an HTTP POST to the URL specified above. An event is any type of update to the reported object, including status or attribute changes. See the events that can be configured in the table below.
Setup while creating payments:
  1. In the notification_url field, indicate the URL from which notifications will be received.
  2. Implement the notifications receiver.
If you want to receive notifications only from Webhook and not from IPN, you can add in the notification_url the parameter source_news=webhook. For example: https://www.yourserver.com/notifications?source_news=webhooks

Note: When you receive a notification on your platform, Mercado Pago waits for a response to validate that you received it correctly. For that, you must return an HTTP STATUS 200 (OK) or 201 (CREATED). If this response is not sent, it will be understood that you have not received the notification and a further attempt to send it will be made until you submit the response.

Production environment

Specific procedure for a merchant to go live:

If the merchant is part of a group of corporations that Mercado Pago follows-up punctually, a call to validate the integration should be made, the test payments in Mercado Pago's system should ve revised, thinking on a progressive roll-out method, etc.


Send feedback

Updated 3 months ago