Setup
Please follow the common dLocal instructions to get set up with card. Next, make sure to enable card as a payment method on your configured account.Capabilities
This connector supports the Mastercard Transaction Link Identifier (TLID). Gr4vy stores the TLID from the first customer-initiated payment and sends it on later merchant-initiated payments, with nothing to enable. dLocal returns the TLID subject to acquirer coverage, so it may be missing for some acquirers.3-D Secure run by dLocal
To have dLocal run 3D Secure (3DS) for a transaction, setconnection_options.dlocal-card.three_dsecure_force to true.
When dLocal returns its 3DS result, Gr4vy records it on the transaction’s three_d_secure object. dLocal only returns the final status, not whether the buyer completed a challenge, so a challenge that passed shows a method of frictionless.
Co-badged cards
Gr4vy doesn’t send a card scheme to dLocal, so dLocal decides which network processes a co-badged card. The dLocal connection has no option to change this.Installments
dLocal supports issuer installments. When a transaction includesinstallment_count, Gr4vy sends it to dLocal as the number of card installments, in card.installments.
The installment counts dLocal accepts depend on the country, issuer, card, and amount. When dLocal doesn’t accept the count you send, it rejects the request rather than declining the payment. The transaction fails with the status authorization_failed and the error_code invalid_request_parameters. If your Flow rule has another connection, Gr4vy tries it next. See dLocal’s installments guide for the plans it offers.