Skip to main content
OVO is a digital wallet used by customers in Indonesia. Customers pay from their OVO account and confirm each payment in the OVO app. Payrails processes OVO through dLocal as the payment service provider (PSP). Open the dLocal guide below for its setup steps and request examples.

​
How a OVO payment works

OVO is a redirect payment method:
  1. The customer selects OVO at checkout.
  2. Payrails returns a redirect URL from dLocal, and the customer goes to OVO.
  3. The customer logs in and confirms the payment in the OVO app.
  4. OVO sends the customer back to your returnInfo URL.
  5. Payrails receives the final result from dLocal and updates the payment.
Each payment is single-use: the customer confirms every payment on its own. Payrails captures OVO payments immediately, so a successful payment is final. To return funds, refund the payment.

​
Supported currencies and countries

OVO supports IDR (Indonesian rupiah) as its only presentment currency.

​
Integrate OVO

The dLocal guide covers the PSP-side setup, the Payrails configuration, and the request fields dLocal requires.

dLocal

OVO via dLocal

​
Check PSPs

​
Ways to integrate OVO

  • Payrails SDK: the Web SDK shows OVO when your workflow returns it as a payment option, and redirects the customer to OVO. To control how the redirect opens, listen for the actionRequired event.
  • Payrails API: call lookup payment options, then authorize with ovo as the paymentMethodCode. The dLocal guide lists the meta fields dLocal requires.
In both cases, confirm the final result through webhook notifications or the execution status. Don’t treat the customer’s return to your success URL as proof of payment.
Last modified on October 5, 2026