payment.md

BricksBuilder.create(brick, target, settings)

Usage example:

mp.bricks().create("payment", "paymentBrick_container", {
  initialization: {
    amount: 10000,
    preferenceId: "<PREFERENCE_ID>",
  },
  customization: {
    paymentMethods: {
      creditCard: "all",
      debitCard: "all",
      ticket: "all",
      bankTransfer: "all",
      mercadoPago: "all",
      atm: "all",
    },
  },
  callbacks: {
    onReady: () => {
      // handle form ready
    },
    onSubmit: ({ paymentMethod, formData }) => {
      return new Promise((resolve, reject) => {
        fetch("/process_payment", {
          method: "POST",
          headers: {
            "Content-Type": "application/json",
          },
          body: JSON.stringify(formData),
        })
          .then((response) => response.json())
          .then((response) => {
            // get payment result
            resolve();
          })
          .catch((error) => {
            // get payment result error
            reject();
          });
      });
    },
    onError: (error) => {
      // handle error
    },
  },
});

Params

brick | string, REQUIRED

Selected Brick. Possible values are: payment.

target | string, REQUIRED

Id of the container that the brick will be rendered in. Can be any HTML element.

settings | object, REQUIRED

The settings object has properties to initialize and customize the brick being created.

Setting key	Type	Description
initialization	object	Defines the initialization data. See more	REQUIRED
callbacks	object	Defines the callback functions. See more	REQUIRED
customization	object	Defines custom properties. See more	OPTIONAL
locale	string	Defines locale.	OPTIONAL

Initialization

Initialization is an object with the properties the brick will initialize with.

Initialization key	Type	Description
amount	number	Defines the transaction amount.	REQUIRED
payer	object	Defines payer initial data. Possible values	OPTIONAL
preferenceId	string	If provided, the brick will bring to screen the Mercado Pago payment option. The preference id should be created in Backend	OPTIONAL

Payer

Payer contains initial payer information.

Payer key	Type	Description
email	string	Defines the payer email. Brick will hide email field if this value is correctly filled
firstName	string	Payer first name
lastName	string	Payer last name
identification	object	Defines payer identification. Contains keys type and number
identification.type	string	Identification type. Possible values vary based on siteId
identification.number	string	Identification number. If filled correctly the Brick will prefill the identification number input
address	object	Defines payer address. Contains keys zipCode, federalUnit,city,neighborhood,streetName,streetNumber and complement
address.zipCode	string	Zip code of payer address. If filled correctly the Brick will prefill the zip code input
address.federalUnit	string	State of payer address. If filled correctly the Brick will prefill the federal unit input
address.city	string	City of payer address. If filled correctly the Brick will prefill the city input
address.neighborhood	string	Neighborhood of payer address. If filled correctly the Brick will prefill the neighborhood input
address.streetName	string	Street name of payer address. If filled correctly the Brick will prefill the street name input
address.streetNumber	number	Street number of payer address. If filled correctly the Brick will prefill the street number input
address.complement	string	Complement of payer address. If filled correctly the Brick will prefill the complement input
customerId	string	Customer ID. View how to manage customers. See More
cardsIds	string[]	Saved Cards Ids. If defined in conjunction with Customer ID, the payer will be able to use their saved cards in checkout. The brick will sort from most recent save card to oldest. If you want the cards not to be sorted, you should add the property preserveSavedCardsOrder explained in this section. For more information about cards ids in Mercado Pago click here.

SiteId	Identification Type Values
MLB (Brazil)	CPF, CNPJ
MLA (Argentina)	DNI, CI, LC, LE, Otro
MCO (Colombia)	CC, CE, NIT, Otro
MLC (Chile)	RUT, Otro
MLU (Uruguay)	CI, Otro
MPE (Peru)	DNI, C.E, RUC, Otro

Callbacks

The callbacks object contains the callbacks functions the brick will call during its life cycle.

Callback key	Description		Params	Returns
onReady	It is called when the brick finishes loading	REQUIRED	void	void
onError	It is called when there is an error in the Brick	REQUIRED	BrickError	void
onSubmit	It is called when the user clicks on the submit button	OPTIONAL	PaymentFormData, AdditionalData	Promise<void>
onBinChange	It is called when the user fills or update card's BIN (first 8 digits)	OPTIONAL	bin	void

BrickError

{
  type: "non_critical" | "critical";
  message: string;
  cause: ErrorCause;
}

ErrorCause

{
  'already_initialized',
  'amount_is_not_number',
  'amount_is_not_number_in_update',
  'card_token_creation_failed',
  'container_not_found',
  'fields_setup_failed',
  'fields_setup_failed_after_3_tries',
  'financial_institution_not_found',
  'get_address_data_failed',
  'get_card_bin_payment_methods_failed',
  'get_card_issuers_failed',
  'get_identification_types_failed',
  'get_mexico_payment_points_failed',
  'get_config_assets_failed',
  'get_payment_installments_failed',
  'empty_installments',
  'get_payment_methods_failed',
  'get_preference_details_failed',
  'get_saved_cards_failed',
  'incomplete_fields',
  'incorrect_initialization',
  'invalid_preference_purpose',
  'invalid_sdk_instance',
  'missing_amount_property',
  'missing_site_property',
  'missing_container_id',
  'missing_locale_property',
  'missing_payment_information',
  'missing_payment_type',
  'missing_required_callbacks',
  'missing_texts',
  'no_preference_provided',
  'no_chunk_path_provided',
  'secure_fields_card_token_creation_failed',
  'settings_empty',
  'translation_key_not_found',
  'unauthorized_payment_method',
  'update_preference_details_failed',
  'validations_parameter_null',
  'get_chunk_failed',
  'get_saved_cards_on_bricks_api_failed',
  'window_redirect_was_blocked',
  'missing_required_review_props',
  'no_payment_method_for_provided_bin',
  'payment_method_not_in_allowed_types',
  'payment_method_not_in_allowed_methods',
  'no_installments_in_selected_range',
  'no_issuers_found_for_card',
}

PaymentFormData

{
  selectedPaymentMethod: "credit_card" |
    "debit_card" |
    "ticket" |
    "bank_transfer" |
    "wallet_purchase" |
    "atm";
  formData: CardData | TicketData | BankTransferData | WalletPurchaseData;
}

Note: The objects CardData, TicketData and BankTransferData could be directly sent to Mercado Pago payment API for processing.

CardData

{
    'token': string,
    'issuer_id': string,
    'payment_method_id': string,
    'transaction_amount': number,
    'payment_method_option_id': string | null,
    'processing_mode': string | null,
    'installments': number,
    'payer': {
        'email': string,
        'identification': {
                'type': string,
                'number': string
        }
    }
}

TicketData

? means the field is optional

{
    'payment_method_id': string,
    'transaction_amount': number,
    'transaction_details'?: {
        'financial_institution': string,
    },
    'payer': {
        'email': string,
        'identification'?: {
            'type': string,
            'number': string
        },
        'first_name'?: string,
        'last_name'?: string,
        'address'?: {
            'city': string,
            'federal_unit': string,
            'neighborhood': string,
            'street_name': string,
            'street_number': string,
            'zip_code': string
        }
    },
    'metadata'?: {
        'payment_point'?: string,
        'payment_mode'?: string
    }
}

BankTransferData

{
    'payment_method_id': string,
    'transaction_amount': number,
    'payer': {
        'email': string
    }
}

WalletPurchaseData

null;

AdditionalData

{
    'bin': string,
    'lastFourDigits': string,
}

Customization

Customizations object is used to load Brick under different conditions.

Customization key	Type	Description
visual	object	Control the visual aspects of the brick. Contains style, font, texts, hidePaymentButton, hideFormTitle, preserveSavedCardsOrder and defaultPaymentOption	OPTIONAL
visual.font	string	Defines the custom font URL. This only applies to the PCI fields.	OPTIONAL
visual.texts	CustomTexts	Defines custom texts for the Brick (available custom texts vary by Brick).	OPTIONAL
visual.style	Style	Defines custom theme and CSS variables	OPTIONAL
visual.hidePaymentButton	boolean	Hides the payment button and disables the onSubmit callback.	OPTIONAL
visual.hideFormTitle	boolean	Hides the form title row.	OPTIONAL
visual.preserveSavedCardsOrder	boolean	When true, the brick will present the cards maintaining the order established in the property initialization.payer.cardsIds.	OPTIONAL
visual.defaultPaymentOption	object	Object that define a single payment method as default, so the form will load with this option already selected. Only one option is allowed. (Can contain one of the following properties creditCardForm, debitCardForm, savedCardForm, ticketForm, bankTransferForm, walletForm, or creditForm)	OPTIONAL
defaultPaymentOption.creditCardForm	boolean	When true, the form loads with credit card selected.	OPTIONAL
defaultPaymentOption.debitCardForm	boolean	When true, the form loads with debit card selected.	OPTIONAL
defaultPaymentOption.savedCardForm	string	One of the cardsIds informed in the property initialization.payer.cardsIds.	OPTIONAL
defaultPaymentOption.ticketForm	boolean	When true, the form loads with ticket selected (check availability)	OPTIONAL
defaultPaymentOption.bankTransferForm	boolean	When true, the form loads bank transfer selected (check availability)	OPTIONAL
defaultPaymentOption.walletForm	boolean	When true, the form loads with Mercado Pago Wallet selected.	OPTIONAL
defaultPaymentOption.creditForm	boolean	When true, the form loads with Mercado Pago Credits selected.	OPTIONAL
paymentMethods	object	Object that allow payment methods configuration. Contains maxInstallments, minInstallments, creditCard, debitCard, ticket, bankTransfer.	OPTIONAL
paymentMethods.maxInstallments	number	Maximum number of installments to be offered to the user	OPTIONAL
paymentMethods.minInstallments	number	Minimal number of installments to be offered to the user	OPTIONAL
paymentMethods.creditCard	string[] or string	Allow payments with credit card. When the value 'all' is provided, all credit cards are accepted. When an array is provided, it should contain the IDs of the desired payment method for the paymentType credit_card.	OPTIONAL
paymentMethods.debitCard	string[] or string	Allow payments with debit card. When the value 'all' is provided, all debit cards are accepted. When an array is provided, it should contain the IDs of the desired payment method for the paymentType debit_card.	OPTIONAL
paymentMethods.ticket	string[] or string	Allow payments with tickets (check availability). When the value 'all' is provided, all ticket methods are accepted. When an array is provided, it should contain the IDs of the desired payment method for the payment type ticket.	OPTIONAL
paymentMethods.bankTransfer	string[] or string	Allow payments with Bank Transfer (check availability). When the value 'all' is provided, all bank transfer methods are accepted. When an array is provided, it should contain the IDs of the desired payment method for the payment type bank_transfer.	OPTIONAL
paymentMethods.atm	string[] or string	Allow payments with ATM methods (check availability). When the value 'all' is provided, all bank transfer methods are accepted. When an array is provided, it should contain the IDs of the desired payment method for the payment type atm.	OPTIONAL
paymentMethods.mercadoPago	string[] or string	Allow payments with Mercado Pago Wallet (available in all countries) and installments without card (only available in Argentina, Brazil and Mexico). When the value 'all' is provided, payments with both are accepted. When 'wallet_purchase' is provided, just payments with Mercado Pago Wallet are accepted and users must log in when redirected to their Mercado Pago account. When 'onboarding_credits' is provided, just payments with installments without card are accepted. In that case, after logging in, will be presented to the user the pre-selected credit payment option in their Mercado Pago account.	OPTIONAL

Custom Texts

Accepted properties are:

Property	Type
formTitle	string
cardNumber	object
cardNumber.label	string
cardNumber.placeholder	string
expirationDate	object
expirationDate.label	string
expirationDate.placeholder	string
securityCode	object
securityCode.label	string
securityCode.placeholder	string
cardholderName	object
cardholderName.label	string
cardholderName.placeholder	string
cardholderIdentification	object
cardholderIdentification.placeholder	string
installmentsSectionTitle	string
selectInstallments	string
selectIssuerBank	string
emailSectionTitle	string
email	object
email.label	string
email.placeholder	string
formSubmit	string
payerFirstName.placeholder	string
payerFirstName.label	string
payerLastName.placeholder	string
payerLastName.label	string
zipCode.placeholder	string
zipCode.label	string
addressState.placeholder	string
addressState.label	string
addressCity.placeholder	string
addressCity.label	string
addressNeighborhood.placeholder	string
addressNeighborhood.label	string
addressStreet.placeholder	string
addressStreet.label	string
addressNumber.label	string
addressComplement.label	string
entityType.label	string
entityType.placeholder	string
financialInstitution.label	string
financialInstitution.placeholder	string

Style

Style is an object with keys for theme and custom CSS variables.

Style key	Type	Description
theme	string	Defines theme for Brick. Possible values: default, dark, flat, bootstrap	OPTIONAL
customVariables	object	Defines custom variables to be applied. Possible values	OPTIONAL

style

{
    theme: 'dark',
    customVariables: {
        textPrimaryColor: 'blue'
    }
}

Custom Variables

Accepted properties are:

Property	Type
textPrimaryColor	string
textSecondaryColor	string
inputBackgroundColor	string
formBackgroundColor	string
baseColor	string
baseColorFirstVariant	string
baseColorSecondVariant	string
secondaryColor	string
errorColor	string
successColor	string
outlinePrimaryColor	string
outlineSecondaryColor	string
buttonTextColor	string
fontSizeExtraSmall	string
fontSizeSmall	string
fontSizeMedium	string
fontSizeLarge	string
fontSizeExtraLarge	string
fontWeightNormal	string
fontWeightSemiBold	string
formInputsTextTransform	string
inputVerticalPadding	string
inputHorizontalPadding	string
inputFocusedBoxShadow	string
inputErrorFocusedBoxShadow	string
inputBorderWidth	string
inputFocusedBorderWidth	string
borderRadiusSmall	string
borderRadiusMedium	string
borderRadiusLarge	string
borderRadiusFull	string
formPadding	string

Note: All sizing properties accept values in: px, rem, em, and %

Ticket availability

Site
MLA (Argentina)
MLB (Brazil)
MCO (Colombia)
MLM (Mexico)
MLU (Uruguay)

Bank Transfer availability

Site
MLB (Brazil)
MCO (Colombia)

ATM availability

Site
MLM (Mexico)
MPE (Peru)

Returns: Promise<BRICK CONTROLLER>

Brick Controller

The Brick Controller contains methods that allow the integrator to interact with the rendered Brick.

unmount	METHOD
getFormData	METHOD
getAdditionalData	METHOD
update	METHOD

Brick Controller.unmount()

The unmount method removes the rendered Brick from the page.

Params

None.

Returns

void

Brick Controller.getFormData()

The getFormData method returns the data the user filled in the form (only works if the submit button is disabled).

Params

None.

Returns

Brick	Return Data
payment	PaymentFormData

Brick Controller.getAdditionalData()

The getAdditionalData method returns additional data that may be useful to you (only works if the submit button is disabled).

Params

None.

Returns

Brick	Return Data
payment	AdditionalData

Brick Controller.update()

When called, the update method updates the given data, preserving the current instance of the brick.

Params

Field	Type	Description	Validation
amount	number	Payment amount. Updating the amount does not affect payments via Mercado Pago Wallet and Installments without card, as their values are defined in the backend.	The new amount must be greater than or equal to the minimum amount allowed by the payment method selected by the user. If validation succeeds, the update method will return true. Otherwise, it will return false.

Returns

boolean

Example

paymentBrickController.update({ amount: 95.32 });