OVO via dLocal

Accept OVO payments from customers in Indonesia with dLocal as the payment service provider (PSP). The customer selects OVO, confirms the payment in the OVO app, and returns to your site.

Supported workflows

Before you begin

Complete these steps before you send your first OVO payment through dLocal:

Set up a dLocal integration in your workspace. Follow the dLocal integration setup guide if you don’t have one yet.
Ask dLocal to enable OVO on your dLocal account for Indonesia.
In the Payrails Portal, go to Settings → Integrations, open your dLocal integration, select OVO under Payment methods, and save.
Add OVO as a payment option in your workflow.

Request fields for dLocal

Send these fields in the authorize request, in addition to the standard authorize fields. Required fields must be present for the payment to succeed. Payrails sends Optional fields to the PSP when you include them.

Field	Status	Description
`amount`	Required	Must be in `IDR`. Payrails rejects OVO requests to dLocal in any other currency.
`meta.customer.name`	Required	Sent to dLocal as the payer name, together with `meta.customer.lastName` when present.
`meta.customer.email`	Required	Sent to dLocal as the payer email.
`meta.customer.country`	Required	Must be present. Payrails sends `ID` to dLocal for OVO.
`meta.customer.lastName`	Optional	Added to the payer name.
`meta.customer.identityCardNumber`	Optional	Sent to dLocal as the payer’s document number.
`meta.customer.phone`, `meta.customer.birthDate`	Optional	Sent to dLocal as payer details.
`meta.customer.reference`	Optional	Sent to dLocal as the payer’s user reference.
`meta.clientContext.ipAddress`	Optional	Sent to dLocal as the payer’s IP address.
`meta.clientContext.deviceFingerprint`	Optional	Sent to dLocal as the payer’s device ID.
`meta.clientContext.clientType`	Optional	`desktop` or `mobile` sends the device type `WEB`, and `app` sends `APP`.
`meta.order.description`	Optional	Sent to dLocal as the payment description.
`meta.order.deliveryAddress`, `meta.order.billingAddress`	Optional	Sent to dLocal as the payer address.

Authorize a OVO payment

Call authorize a payment with ovo as the paymentMethodCode. The response includes the redirect to OVO.

Authorize request

{
  "amount": {
    "value": "150000.00",
    "currency": "IDR"
  },
  "paymentComposition": [
    {
      "integrationType": "api",
      "paymentMethodCode": "ovo",
      "amount": {
        "value": "150000.00",
        "currency": "IDR"
      }
    }
  ],
  "meta": {
    "customer": {
      "name": "Putri",
      "lastName": "Wijaya",
      "email": "putri.wijaya@example.com",
      "country": {
        "code": "ID"
      }
    },
    "clientContext": {
      "ipAddress": "203.0.113.10"
    }
  },
  "returnInfo": {
    "success": "https://example.com/success",
    "error": "https://example.com/error"
  }
}

After the customer confirms the payment, OVO returns them to your success or error URL. Confirm the result through webhook notifications or the execution status before you fulfill the order.

How dLocal handles OVO

Payrails sends OVO to dLocal with Indonesia as the payment country, whatever country code the request carries.
Payrails removes digits, punctuation and symbols from the payer name before it sends the name to dLocal.
Payrails sends meta.order.deliveryAddress to dLocal as the payer address. If the request has no delivery address, Payrails sends meta.order.billingAddress.

Getting Started

Payment Orchestration

Token Vault

Analytics & Reporting

Fraud Management

Chargebacks

Monitoring

Resources

Use Cases

Supported workflows

Before you begin

Request fields for dLocal

Authorize a OVO payment

How dLocal handles OVO

​Supported workflows

​Before you begin

​Request fields for dLocal

​Authorize a OVO payment

​How dLocal handles OVO

Supported workflows

Before you begin

Request fields for dLocal

Authorize a OVO payment

How dLocal handles OVO