Skip to main content

​
SDK flow

1

Build the request

Configure the operation, currency, billing data, and optional features.
2

Select the environment

Use Development during integration and switch to Production only after certification.
3

Authorize

The SDK runs risk assessment, 3DS authentication when applicable, and authorization.
4

Process the response

Observe internal actions and update the order only from the final response.

​
Integration environment

  • Available 24 hours a day, Monday through Sunday.
  • Support from 09:00 to 18:00 on business days.
  • Times are expressed in Peru time, GMT-5.
  • Test results must be sent to the responsible integration specialists.

​
PaymeRequest structure

​
Settings

  • locale: es_PE or en_US.
  • brands: VISA, MSCD, AMEX, and DINC, according to merchant configuration.

​
Operation

​
Person data

PaymePersonData contains first name, last name, email, address, alphabetic and numeric country codes, ZIP code, city, state, and mobile phone. addrLine2, home phone, and work phone are optional.

​
Optional features

  • reserved: additional merchant data.
  • wallet: Wallet must be enabled; userID is required when enable is true.
  • installments: enables plans and installments configured for the merchant.
  • authentication.tdsChallengeInd: 3DS preference (01 no preference, 02 no challenge, 03 challenge preferred, 04 challenge required).
Enable Wallet, installments, or 3DS only when the corresponding service is configured for the merchant. Never include the merchant Key in source control or diagnostic logs.
Continue to responses and errors →