name
email
birth_date
phone
document
document2
user_reference
address
ip
device_id
device_id
see the Device ID documentation. Required for fraud prevention. state
city
zip_code
street
number
"save": true
and use the card_id
from the response for future payments. card_id
or token
should use the endpoint: https://api.dlocal.com/paymentsholder_name
token
or card_id
not presentexpiration_month
token
or card_id
not presentexpiration_year
token
or card_id
not presentnumber
encrypted_data
,token
or card_id
not presentcvv
cvv_token
installments
installments_id
descriptor
capture
TRUE
. Optional.save
card_id
. Learn more.​token
:card_id
from Create a Card method:holder_name
email
document
cbu
number
and cvv
parameters with encrypted_data
.token
. To make a payment with a card_id
obtained from the Create a Card method, simply replace the token
parameter with card_id
.description
field. Learn more here.​PENDING
PAID
REJECTED
CANCELLED
EXPIRED
AUTHORIZED
VERIFIED
REJECTED
REJECTED
REJECTED
REJECTED
REJECTED
REJECTED
REJECTED
REJECTED
REJECTED
REJECTED
REJECTED
REJECTED
REJECTED
REJECTED
REJECTED
REJECTED
REJECTED
REJECTED
REJECTED
PENDING
PENDING
code
message
param
403 Forbidden
404 Not Found
400 Bad Request
notification_url
field of the payment, if it differs from the one specified in the merchant panel. The body of the request will always be the payment object.Authorization
HTTP header from the notification, and compare it with the one generated by you using your X-Login
and secretKey
, and the X-Date
and Request body of the notification received. If the signature generated by you matched the one received on the Authorization
HTTP header, then it is safe to assume that this is a valid message from dLocal.