Create payment lock

Decodes a payment destination and locks the conversion price needed to execute it. If the destination needs an amount and none is provided, the service returns HTTP 206 with recipient details and no usable lock code.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string

Optional user id, numberId, or externalId. When omitted, the service resolves the company principal user for the destination country.

string
required

QR string, payment code, PIX key, or supported payment destination. qrCode is also accepted.

string

Amount to pay. Required for destinations that do not encode an amount.

string

Asset charged to the user/company. Defaults to USDT.

string

Optional preferred public payment network.

string

Optional destination country/exchange hint.

sender
object

Real payer. legalId must match the payer country's format. An Argentine payer may also send a passport (e.g. AAA123456) when the QR is from another country; QR payments in Argentina still require CUIT or DNI. Payments with a fiat against that require a deposit still need CUIT or DNI.

string

Optional blockchain address the payment will be funded from. When provided, the address is screened before the lock is created and the request is rejected with a 403 RISKY_SOURCE_ADDRESS error if the address is considered too risky. Requires sourceNetwork.

string

Blockchain network of sourceAddress. Required when sourceAddress is provided. Networks that cannot be screened are rejected with a 400 UNSUPPORTED_BLOCKCHAIN error.

Headers
string
required

Your Manteca API key.

Responses

400

Invalid payment destination or request.

409

User not validated or blocked.

429

Payment lock rate limit reached.

503

Payment provider unavailable.

Language
Credentials
Header
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json