- Previous Steps
- Setting Credentials
- Getting Payment Methods and Identification Types
- Payment Procedure
- Create a card token
- Search for Customer
- Create Customer if it does not already exist
- Create Payment
- If successful, associate the card with the user in MercadoPago
When using custom checkout, the user never leaves the seller’s site.
See Setting Mercado Pago credentials
You need to get the available payment methods and identification types (both vary depending on the seller’s country).
Payment Methods refer to credit cards, debit cards, MercadoPago credit, ticket, cash, etc.
Identification types refer to which method of identification is going to be used for the user (varies according to the country)
You can get the available Payment Methods as follows:
where the variable’s type is PaymentMethodsSDT. The procedure will return the information loaded into that variable.
You can now load the payment methods to a combo box
for &p in &PaymentMethodsSdt
&p is PaymentMethodsSDT.PaymentMethodsSDTItem type
&MetPago is VarChar(100), type combobox.
The same applies to Identification Types:
for &t in &TypesIdentificationSDT
&t = TypesIdentificationSDT.TypesIdentificationSDTItem
&type = Character(20)
Note: Some countries (Ex: Mexico) don’t have identification types.
When you opt for payment by credit or debit card, there are two important security-related considerations:
- To make the payment, you must first obtain a Token from the card details.
- There is a method to obtain the token from the data on the card, but the card information cannot travel through servers other than PCI Compliant. In such cases, it should be sent directly to the MercadoPago's server from your client-side application. For security reasons, it is very important that these data never reach your servers.
The GeneXus SDK has a different approach for creating the card token depending on whether you are performing the checkout process from a Web or Smart Device application.
In your Web Panel for Checkout, you must include a WebComponent (found on the SDK, named "WCCreditCardPayment"), which contains the necessary protected fields to create a card token (name, credit card number, security code, expiration month, expiration year).
Important Note: You must not change the variables' name in this WebComponent.
Msg("Payment Fail - " + &TokenError)
FormatError is returned when one or more required fields are empty. &ErrorMessage contains a description of the problem.
TokenFail is returned when a problem occurs on MercadoPago's API, (ex: wrong credit card number). &TokenError also contains information about the problem
TokenReady is returned when the token was generated correctly. &CCToken is the token's id, used later in the payment preference.
The rest of the payment's procedure must be programmed inside TokenReady event, as it is only executed when a valid credit card token is available.
In order to obtain the card token from a Smart Device Application, an External Object called MercadoPagoCheckout needs to be used. This external object allows you to send card information and get the corresponding token in a secure way, interacting directly with Mercado Pago's server.
The MercadoPagoCheckout External Objects has two methods:
Receives the type of card as a parameter (Visa, Master, etc. - this is a list of payment methods), card number, CVV, owner name and document (identification type), card expiration month and year.
It returns an SDT containing the response of MercadoPago servers with the token generated for the card along with the last four digits of the card, or an error code in case of failure, defined in the MercadoPagoErrorCode domain:
Receives the card_id of a previously saved card for the customer with their CVV and returns an SDT containing the response of MercadoPago servers with the token generated for the card along with the last four digits of the card, or an error code in case of failure, defined in the MercadoPagoErrorCode.
Warning: To use this method, you need to set the Public Key and Access Token Mercado Pagos's properties in the main Smart Device object.
To get these values, see Setting MercadoPago Credentials
You must search for the user (in MercadoPago) using the SearchUser procedure where &Email is the user you want to search for e-mail.:
//If &ErrorCode = 0 you load the user
for &s in &SearchUserSDT.results
&user.UserId = &s.id.Trim()
&user.UserMPId = &s.id.Trim()
&user.UserEmail = &s.email.Trim()
&user.UserForTest = false
&user.UserType = UserType.Buyer
&SearchUserSDT is a SearchUserSDT variable.
Note: &user is a User type variable (transaction in which users are stored in your DataBase).
Note: User is an example transaction, each developer may create the user with the attributes it prefers.
//If &ErrorCode is not 0 (this means the user was not found), then you have to create a user (in MercadoPago):
if &ErrorCode = 0
&user = new()
&user.UserId = &ClientSDT.id.Trim()
&user.UserMPId = &ClientSDT.id.Trim()
&user.UserNickName = &ClientSDT.nickname.Trim()
&user.UserPassword = &ClientSDT.password.Trim()
&user.UserEmail = &ClientSDT.email.Trim()
&user.UserForTest = false
&user.UserType = UserType.Buyer
Now you have to create the payment
&PaymentSDT = new()
&PaymentSDT.token = &CCToken
Complete the information about the payment:
Add items to the payment
&Item type: CreatePaymentSDT.additional_info.itemsItem
&Item = new()
To create the payment, there is a procedure
If &ErrorCode = 0
ErrorCode = 0 means the payment was successful, you can then, associate the buyer to their credit card (in MercadoPago).
When payment is successful, you can add a security check, to test if credit card information went through the server or not (for Web Checkout)
This global event is executed in the Web Component included before.