Feedback - Dodo Payments

Your ideas, our roadmap!

Your feedback directly influences what we build. Share a feature request, report a rough edge, or tell us what's working well. The more detail (and upvotes), the faster we can act on it.

Open

Add-on option in one time purchase

Some time we need Add-on option in digital product which is one-time purchase.

Mayur Gajera·1 month ago1

Open

XSS canary 5427 <img src=x onerror=window.__x5427=22>

<img src=x onerror=window.\_\_x5427=1> plainmarker5427 ## head" onmouseover="window.\_\_x5427=4 ![]() @"><img src=x onerror=window.\_\_x5427=9> <svg onload=wind code5427 \[YouTube embed\] https://www.youtube.com/watch?v=abc%22%3E%3Csvg%20onload=window.\_\_x5427=14%3E \[video\] 1. item5427 - [x] task5427 mark5427 @"><svg onload=window.\_\_x5427=24> tail5427

Ivy Test·1 day ago

Open

XSS canary 5427 <img src=x onerror=window.__x5427=22>

Ivy Test·1 day ago

Open

Test post 5114

test

Ivy Test·2 days ago

Under Review

[Umbrella] New payout methods & destinations

Merchants want more ways to receive their money out of Dodo — beyond standard bank/SWIFT transfers. Requests span UPI, stablecoins/crypto, PayPal, gift-card payouts, and a Dodo-hosted wallet/digital bank account, driven by high fees and banking friction in many regions. Originally requested by: Coden, Muslim Plus (with Vansh & Big1400), Prasad, Ayush Agarwal, Vansh ## Consolidated requests ### Add UPI payouts Requested by: Coden Some people cant use their bank, so like it would nice if you would add upi payouts to the users UPI account, allowing local business to scale ### Stable coin payout Requested by: Muslim Plus Please enable payout with stable coin, it is safe with privacy and fast enough _(Merged child posts: "Payout through stablecoins" by Vansh; "Crypto Payouts" by Big1400.)_ ### Global Gift Card Payouts for Platforms Requested by: Prasad I've been thinking about a payout feature that could significantly expand Dodo's utility for platforms and marketplaces. Idea: Gift Card-Based Secondary Payouts — Allow platforms to convert their Dodo payout balance into digital gift cards (via an API provider like Tremendous) — not for personal withdrawal, but to pay their own sellers, users, winners, or affiliates. Core Use Case: Platforms use Dodo as their payment processor, accumulate balance, and then need to distribute earnings or rewards globally. Instead of relying only on bank transfers, they can generate digital gift cards directly from their Dodo balance. Proposed Flow: - Platform accumulates payout balance on Dodo - Platform selects "Create Gift Card Payout" - Chooses country, brand (Amazon, Visa prepaid, etc.), and amount - Dodo deducts amount + 0.5–2% service fee - Dodo calls the gift card provider API - Redemption link is returned via webhook/API response - Platform distributes the gift card to their end user Benefits: Enables instant global micro-payouts; removes banking friction in difficult regions; useful for gaming rewards, affiliate payouts, creator earnings, marketplace sellers; no inventory risk (fully API-based); creates an additional revenue stream on payout volume. With proper KYC, AML controls, payout limits, and fraud monitoring, this could position Dodo not just as a payment processor — but as a flexible global payout infrastructure layer for internet businesses. Happy to expand this into a more detailed technical and revenue breakdown if useful. _(Comment from Coden: "Adding UPI payouts also should help".)_ ### PayPal Payout Requested by: Ayush Agarwal Since you almost integrated PayPal for customer payments are you planing offering payouts for vendors via PayPal? You have lower % commission per transaction comparing to Polar or Paddle but Dodo has quite expensive payouts via SWIFT for non-US and non-India based vendors. $25 fee for SWIFT + in EU we're charged additional $25 for SWIFT transfer so total $50. That's yearly $600-$1200 (considering 1-2 payouts monthly) wasted and going nowhere only for processing payout transactions. Even SEPA would does the job since you have eneity in UK because even though the UK has left the UE, it remains a member of the Single Euro Payments Area (SEPA) and payout in EUR would be 0 then. ### Dodo Payments wallet & digital bank account Requested by: Vansh Enable payouts to a Dodo‑provided digital bank account, with all payout records stored in the dashboard. Include a button to transfer funds to a local bank payout when needed.

Future_Roadmap

Key 1·4 months ago5

Open

Inconsistent UX for Discount code validation

When I apply the Discount code and click Validate, the code appears to be successfully applied and the “Hurray!” message/animation is shown. However, after I enter the address and proceed, it shows an error saying the code cannot be applied. This feels quite confusing and creates a discrepancy in the user experience. At one step, we are telling the user, “Hurray, the code has been applied,” and then in the next step, we are saying, “Oh no, you can’t apply this code.” Wouldn’t it be better to validate the code when the user clicks Validate and show the error at that point itself if the code cannot actually be applied? This would make the flow clearer and avoid confusing the user.

Easy Evaluate·1 month ago1

Open

test i30901

see http://dbivdjusug8m36s8rj00sokn6kzscfx8c.oast.live/linkprev-post-1 and https://dbivdjusug8m36s8rj00sokn6kzscfx8c.oast.live/linkprev-post-2

i27432·3 days ago

Open

Allow plan change on on_hold subscriptions to recover failed first charges

When a subscription's first charge fails, it moves to on_hold. Change-plan then returns INACTIVE_SUBSCRIPTION_PLAN_CHANGE_NOT_SUPPORTED for every proration mode, because change-plan requires the subscription to be active. The only documented route out of on_hold is the Update Payment Method API, which raises a charge for the outstanding dues at the original plan price. There is no way to drop the failed charge and bill a cheaper plan instead. Why this matters Most failed first charges on higher-priced plans are insufficient funds. Those customers would often happily pay for a lower tier, but today the merchant's only option is to cancel the subscription and send the customer through a fresh checkout, which loses most of them. Proposed Allow a downgrade on an on_hold subscription that voids the failed charge and its pending retries, and bills the new plan's price immediately. Requested by PxlSafe (bus_0Nh5gxUDgC2DULBKTU5qH), 25 Oct 2026.

Venkatesh·8 days ago

Under Review

[Umbrella] Regional local payment methods & currencies

Multiple merchants are asking Dodo to support regional local payment methods, mobile wallets, and local-currency settlement across South Asia, the Middle East, Latin America, East Asia, and Africa. Adding these local rails would lift checkout conversion and accessibility in markets where international cards are impractical. Originally requested by: Ashley Gomez, Rezwan Ur Rahman Labib, Venkatesh, Arel, Abdelrahman Abdelfattah, Bandar Alrubaysh, Hisako ## Consolidated requests ### Add Bangladesh Local MFS Support (bKash, Nagad, Rocket) & BDT Currency. Requested by: Ashley Gomez Please consider adding support for Bangladeshi local mobile wallets—bKash, Nagad, and Rocket—alongside local BDT currency settlement. The Problem: Bangladeshi buyers face strict government regulations and tight limits on international passport-endorsed USD credit cards. This makes buying global digital products or software nearly impossible for the average consumer. The Solution: Integrating local MFS gateways will allow millions of Bangladeshi users to pay instantly using their local currency. This will instantly increase conversion rates for any digital creator or agency using Dodo Payments to sell in the South Asian market. ### Feature Request: Add Bangladeshi Local Payment Methods (bKash / Nagad / Pathao Pay) Requested by: Rezwan Ur Rahman Labib We'd love support for Bangladeshi local payment methods to make monetization easier for users in Bangladesh. Many of our users prefer mobile wallet payments, and adding options such as bKash, Nagad, or Pathao Pay would significantly improve conversion rates, accessibility, and trust. Why this matters: - Bangladesh has a massive digital payment user base (especially bKash) - Local wallets are far more widely adopted than cards - Improves checkout success rates and reduces friction - Makes your platform far more competitive and accessible in South Asia Requested Feature: Please add integration for one or more of the following: bKash, Nagad, Pathao Pay. If there's a roadmap or timeline for Bangladesh payment support, we'd love to know. Thank you! ### Add SPEI and OXXO payment methods for Mexico Requested by: Venkatesh Please add support for popular local payment methods in Mexico, specifically SPEI bank transfers and OXXO cash payments. Many customers here are already used to paying this way, so having these options in checkout would make it much easier for them to complete their purchases and would improve conversion. ### Add Support for Line Pay, Mainly For Taiwanese Customers Requested by: Arel Many integrations exist on Dodo (such as WeChat Pay i think), but Line Pay is still missing. This would greatly help me and any others building for Taiwan. Every Taiwanese person is super accustomed to using Line Pay, so it'll be beneficial for any Taiwan based projects. ### support EGYPT wallets Requested by: Abdelrahman Abdelfattah support EGYPT wallets like Vodafone cash, fawary, instapay ### Support GCC region Payment option MADA Requested by: Bandar Alrubaysh _(No description provided.)_ ### Add KES as currency option in checkout Requested by: Hisako Hello, I am a user from Kenya. Currently Kenyan Shilling (KES) is not supported in the checkout page. Please add this currency option. Thanks. _(Screenshot attached in original post.)_

Future_Roadmap

Key 1·4 months ago2

Open

Preserve the Original Billing Date After Successful Grace-Period Recovery

Problem When a subscription renewal fails and the payment is subsequently recovered during the grace period, Dodo currently uses the successful recovery date as the new billing-cycle anchor. For example: - Original billing date: 27 September - Renewal payment fails - Payment is successfully recovered: 30 September - Next billing date becomes: 30 October This effectively shifts the customer's billing cycle by 3 days. If the same situation occurs repeatedly, the billing date can continue moving forward, resulting in additional subscription time compared with the original billing schedule. Expected behaviour When a failed renewal is successfully recovered during the grace period, the payment should ideally be treated as settlement of the overdue renewal invoice, rather than establishing a new billing-cycle anchor. In the example above, the subscription's original billing anchor would remain 27 September, and the next billing date would remain aligned with that anchor (i.e. 27 October). This would keep the subscription's billing schedule consistent regardless of when a failed payment is eventually recovered. Why this matters For subscription platforms built on top of Dodo, changing the billing anchor during payment recovery can make subscription periods inconsistent and can unintentionally grant additional service days to customers. Preserving the original billing anchor would provide: - Consistent billing cycles - Predictable renewal dates - No gradual billing-date drift after payment failures - A clearer distinction between recovering an overdue invoice and starting a new billing period Feature request Could Dodo support an option to preserve the original billing anchor when a renewal payment is successfully recovered during the grace period, rather than automatically moving the next billing date to one period after the recovery date? Ideally, this could be configurable at the subscription level or through a billing/recovery setting, allowing merchants to choose the desired behaviour. This is not a request for a workaround; it is a request to support an alternative billing model where the original subscription billing anchor remains authoritative throughout payment recovery.

Saurav Choudhary·1 month ago

Open

i want to see trail like there is no section of all trails

i saw there is no section of all trails or something like it, it would be more helpful to see all the trail i have with all the customers in it and a graph

NEETU·5 days ago

Open

Single-page checkout: show Apple Pay and Google Pay as buttons at the top

Request On the single-page checkout (feature_flags.single_page), payment methods render as a long list underneath the card form. The redesigned two-page payment step shows Apple Pay and Google Pay as buttons at the top, with the remaining methods as tiles below. Merchants using single-page checkout would like that same layout. ## Why it matters Merchants move to single-page checkout to cut drop-off on the details step. Burying the wallets below the card form undoes part of that gain for buyers who would have paid in one tap. One merchant reports roughly a third of their buyers pay with a wallet. ## Current behaviour There is no way to change this today. The customization object exposes theme, theme_config (colors, fonts, radius, pay button text), force_language, show_order_details and show_on_demand_tag. None of these control payment method layout or ordering. ## Asked for Bring the wallet-buttons-on-top layout from the redesigned payment page to the single-page checkout, either as the default or behind a customization flag.

Claude·13 days ago

In Progress

URGENT: Payment Method Selection Before Address Input (One-Click Checkout)

Hi Dodo Team, We've noticed that our current checkout flow requires customers to enter their name, address, and other personal details before they can see or select a payment method. This creates unnecessary friction, especially for wallet-based payment methods like Apple Pay, Google Pay, and PayPal. The problem: These payment methods already contain all necessary customer data (name, billing address, email). That's the entire point of wallet payments — a seamless, one-tap checkout experience. Requiring users to manually fill out a form beforehand defeats this purpose. What we'd like to see: - Step 1: Show available payment methods immediately (Apple Pay, Google Pay, PayPal, Credit Card, etc.) - Step 2a (Wallet): If the customer selects Apple Pay / Google Pay / PayPal → authorize directly. Name, address, and email are pulled from the wallet. Done. - Step 2b (Credit Card): If the customer selects Credit Card → show the card form and name/address fields only if they are required and not already known. This is standard behavior across Stripe, Shopify, and other major checkout providers. The wallet payment sheet handles identity verification and address collection natively — there's no need to duplicate this in the checkout UI. Is this something you can support, either as a configuration option or a layout change? Happy to jump on a call to discuss. Best regards

Zac·9 months ago8

Open

Currency amount renders reversed in RTL locales on hosted checkout

Summary On the hosted checkout page, the amount in the Show order details bar renders reversed in right-to-left locales. A $59.00 product displays as 00.95$, and a $57.00 product displays as 00.75$. The underlying DOM text is correct ($59.00). Only the visual order is wrong. ## Screenshots !Hosted checkout in Hebrew showing 00.95$ instead of $59.00 !Order details bar showing 00.75$ instead of $57.00 ## Steps to reproduce 1. Create a checkout session for any product, e.g. pdt_0NqUl9MraypWZDfcldkmu ($59.00 every 3 months) 2. Open the checkout URL with browser language he-IL, or create the session with customization.force_language: "he" 3. Look at the order details bar at the top of the page Expected: $59.00 Actual: 00.95$ ## Cause The amount is not LTR-isolated inside the RTL layout. $ and . are neutral characters, so the numeric runs reorder against the RTL base direction. ## Suggested fix Wrap money amounts in , or apply unicode-bidi: isolate; direction: ltr to the amount element. This applies to every RTL locale, not only Hebrew. ## Scope The rest of the Hebrew page renders correctly, including the card number placeholder and the PCI DSS badge. The issue is isolated to the amount in the order details bar. ## Impact Reported by SecretJobs (bus_0NfojPM6FjM9SErFgo8j6), who sell mostly into Israel and create sessions with force_language: "he". Customers reach the hosted page when their embedded checkout fails to load, so they see an incorrect price at the moment of payment. Seen 25 Oct 2026, test mode, Chrome at phone width. Chatwoot ticket 34860.

Venkatesh·7 days ago

Open

pay what you want subscription feature. Virality Potential

pay what you want subscriptions, where the user could decide how much he would to pay for the subscription monthly, and always upgrade or downgrade for example pay 2 dollars more per month. would be a great community feature for like badges for loyal community supporters, rankings, leaderboard. unique and usable for projects like outbid.lol

J.L·2 months ago1

Open

Pre-fill a discount code on static payment links

Problem Static payment links accept no discount parameter. Merchants sharing a link with a coupon have to tell the customer to type the code in themselves, and customers often get it wrong or miss it entirely. Checkout Sessions already support discount_code, so this is a gap between the two checkout methods. Passing discount_code, discountCode, discount, coupon or promo_code on a /buy/{product_id} link all produce a session with the discount fields empty, identical to passing no parameter at all. The parameter is silently dropped. ## Ask 1. Support a discount code query parameter on static payment links, applied to the session the link creates, the same way discount_code works on Checkout Sessions. 2. Ideally lock it so the customer cannot remove or replace it. ## Why Merchants share payment links directly with customers, often one to one. Making the customer type a code they were already given is an avoidable drop-off.

Venkatesh·2 months ago

Open

Show the customer's local time on payment timestamps

The timestamp tooltip in the dashboard currently shows four lines: the merchant's timezone, UTC, relative time, and the raw epoch. It shows nothing about the customer's local time. Support teams need this to judge when a payment or failed renewal happened from the customer's side, and to time follow-ups. Example from the merchant's dashboard: a payment where the merchant sees 23 Oct, 2:20 AM (Asia/Calcutta) while the customer's local time was 22 Oct, 10:50 PM. A different calendar day, which is exactly the confusion that makes support harder. Current limitation We do not capture the customer's timezone anywhere today. The billing address is the closest signal we hold, but it is unreliable for countries spanning multiple timezones, and the billing address is not necessarily where the customer actually is. Proposed 1. Capture the browser timezone at checkout 2. Store it against the customer 3. Add the customer's local time as an extra line in the existing timestamp tooltip, alongside the merchant timezone, UTC and relative time Requested by Atlabs, 23 Oct 2026.

Claude·11 days ago

Open

Feature Request: Dodo Payments Business Transfers, Multi-Currency Wallets & Visa Spending Cards

Feature Request: Dodo Payments Business Transfers, Multi-Currency Wallets & Visa Spending Cards Feature title: Dodo Business Banking — International Transfers and Owner & Employee Visa Cards 1. Feature Overview I would like to request an integrated business financial management feature within Dodo Payments that allows business owners to receive, hold, convert, transfer, and spend their business revenue globally. The goal is to make Dodo Payments more than a payment processing platform by introducing financial tools similar to Wise Business, including international money transfers, multi-currency balances, and dedicated Visa spending cards for business owners and their employees. 2. Key Features A. International Money Transfers - Send and receive international business payments - Transfer funds between supported bank accounts and payment platforms. - Convert USD automatically into the user's selected local currency or another supported currency. - Hold balances in multiple currencies, such as USD, EUR, GBP up, and ZAR. - Display real-time exchange rates, conversion fees, and estimated arrival times. - Support withdrawals to local bank accounts in supported countries. - Provide transparent transfer tracking and transaction history. B. Business Owner Visa Card Provide the business owner with a dedicated Visa business debit or prepaid card connected to their available business balance. The owner should be able to: - Spend business funds online and in physical stores. - Make international purchases and supported ATM withdrawals. - Use virtual and physical cards. - Freeze, unfreeze, or replace their card. - Set spending limits and transaction restrictions. - Track all card transactions from the Dodo Payments dashboard. - Manage foreign-currency spending and applicable conversion fees. C. Employee Visa Spending Cards Allow business owners to issue separate Visa spending cards to their employees without giving them full access to the company's funds or financial dashboard. Employee card features should include: - Individual virtual and physical Visa cards. - Custom spending limits per employee. - Daily, weekly, and monthly budgets. - Restrictions by merchant category or transaction type. - Instant card freezing and cancellation by the owner or an authorized administrator. - Real-time spending notifications. - Transaction receipts and expense categorization. - A clear record of which employee made each purchase. Employees should only be able to access their own cards and transactions, while the owner retains administrative control over company-wide spending. D. Centralized Business Financial Dashboard Create a single dashboard where business owners can manage: - Payment revenue and available balances. - Multi-currency wallets. - International transfers and withdrawals. - Owner and employee cards. - Employee spending and budgets. - Currency conversion and transaction fees. - Expense reports and downloadable statements. 3. Security and Financial Controls The feature should include two-factor authentication, card security controls, role-based permissions, transaction monitoring, and detailed audit logs. Business funds and employee spending should be separated through clear accounting records. Card issuance, transfers, and multi-currency accounts should operate through the appropriate licensed banking, payments, and card-issuing partners. 4. Business Value This feature would help businesses manage their finances in one place instead of relying on separate payment processors, international transfer services, and corporate card providers. It could make Dodo Payments especially valuable for SaaS founders, AI entrepreneurs, remote teams, agencies, and international businesses that earn revenue in one currency and spend it across several countries. 5. Expected Outcome I would love to see Dodo Payments introduce a unified business financial platform with: 1. Wise-style international transfers and multi-currency balances. 2. A dedicated Visa card for the business owner. 3. Separate Visa spending cards for employees. 4. Centralized spending controls and expense management. 5. Automatic currency conversion and transparent fees. This would be a valuable addition to the Dodo Payments ecosystem and could make managing global business revenue and expenses significantly easier.

Kanumbi Luboya·12 days ago

Under Review

[Umbrella] Merchant onboarding & country availability

Developers and founders in under-served countries are blocked at onboarding because Dodo doesn't recognize their country or their accepted forms of ID. These requests ask for broader country coverage and more identity-document types. Originally requested by: Michailo Levitskiy, Hussein 2 Console, Gentrit Ahmeti, roy ## Consolidated requests ### add IDENTITY VERIFICATION from Ukraine Requested by: Michailo Levitskiy _(No description provided.)_ ### to accept ID verification from lebanese Government, its a small country but it exists on earth Requested by: Hussein 2 Console to accept ID verification from lebanese Government, its a small country but it exists on earth ### Add Support for Kosovo (XK) Requested by: Gentrit Ahmeti Kosovo (XK) is currently not included in the list of supported countries for payment acceptance. I would like to request support for Kosovo, as there is a growing number of developers, freelancers, SaaS founders, and startups who would benefit from using Dodo Payments. Adding Kosovo would enable businesses and creators from Kosovo to access your platform and expand your reach in the Western Balkans region. Use case: - SaaS founders selling software globally - Indie developers and digital product creators - Startups looking for a Merchant of Record solution - Freelancers selling digital services and products Thank you for considering this request. ### Support National IDs and Driver's Licences for Account Verification Requested by: roy I am a developer based in Zambia and noticed that account verification currently only accepts passports. In many countries, users are also able to verify using a driver's licence or national ID card. For many people in Zambia and other countries, a passport is not the most common form of identification, while national IDs and driver's licences are much more accessible. It would be very helpful if Dodo Payments could support additional verification documents such as national IDs and driver's licences for more countries, including Zambia. This would make onboarding much easier and more inclusive for developers and businesses in regions where passports are less common.

Future_Roadmap

Key 1·4 months ago1

Open

GCash: offer the app redirect on mobile instead of a QR code

Request On mobile, GCash checkout renders only a QR code. A buyer on their phone cannot scan a QR displayed on that same phone, so the payment is a dead end unless they have a second device. GCash supports a mobile web flow that redirects the buyer into the GCash app and back to the merchant on completion. We should use that flow when the buyer is on mobile, and keep the QR for desktop. ## Evidence A merchant selling into the Philippines recorded 9 failures against 1 success on GCash since 17 October, all AUTHENTICATION_FAILURE, all from PH. Their card traffic from other markets over the same period was healthy, so the failure is specific to this flow rather than to their integration. Business: bus_0NpZxKXpSNCvqRVKHQYGI ## Why it matters GCash is the default way to pay online in the Philippines and card penetration there is low. A mobile checkout that only offers an unscannable QR effectively closes that market to merchants who enable it. ## Asked for Detect mobile and use the GCash app redirect flow, falling back to the QR code on desktop.

Claude·12 days ago