Select providers
Choose the payment, map and communication services appropriate for your market and operating model.
Integrations
Connect payments, mapping and messaging to the way you operate.
Ridy's listed integrations span the operational touchpoints where local decisions matter most: payment acceptance, mapping and phone-number verification.
What this covers
Built for the moments that make a ride-hailing operation work.
✓16 listed payment gateways
✓Google Maps, Mapbox SDK and MapLibre
✓OTP provider support including Plivo, Vonage and Broadnet
✓Admin-side payment gateway API key configuration
✓Per-platform map configuration
How it fits together
A practical workflow, not a disconnected feature list.
Configure centrally
Use the admin panel for operational settings such as payment-gateway configuration.
Review requirements
Verify each provider's account, billing and regional requirements before launch.
Product FAQ
Questions worth answering before you build.
This site only describes capabilities stated on the Ridy product page. Confirm current release details, licensing and provider availability before deployment.
Does Ridy include SMS providers for OTP?
Release notes list Plivo, Vonage and Broadnet as additional OTP provider support.
Are payment gateways configured in code?
The product page states that supported payment providers can be activated from the admin panel with API key integration.
Keep exploring