Add-on option in one time purchase

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

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.

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.

[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.

instant payout

we are able to take payouts instantly after a coupling payouts on demand so we can have more freedom and be able to invest in the business quicker

Our app sells 5 credits, but Dodo Payments' checkout confusingly displays "5 Talk Rightly Credits" alongside the default "Includes 1 credit." This conflicting messaging risks user drop-offs.

Refunds: allow entering the refund amount in the original transaction currency

Refunds can only be entered in the settlement currency (USD), not in the currency the payment was taken in. Merchants who raise credit notes in the original currency have to convert to USD for every refund, and still cannot land on an exact figure. Reported by Cuemath (Asif Hussain) for AED transactions. They have this option on their other payment gateways. ## Verified in test mode Payment of EGP 1,145.49, settling as USD 21.17: - GET /payments/{id}/line-items returns currency: "USD" with refundable_amount: 1902 - POST /refunds with amount: 500 succeeded - Response: amount: 26345, currency: "EGP" - Line items after: refundable_amount dropped 1902 to 1402 So the input is read as USD 5.00 and the customer receives EGP 263.45. There is no currency field on POST /refunds, and supplying one is ignored. This applies to both the dashboard and the API. ## Why this matters beyond the manual conversion Because the conversion happens at refund time using our rate, the merchant cannot target an exact amount in the original currency. A USD 5.00 refund produced EGP 263.45. If a credit note is raised for AED 250.00, there is no USD input that reliably produces exactly AED 250.00, so the credit note and the actual refund will not reconcile. ## Ask Allow the refund amount to be entered in the original transaction currency, in the dashboard and via a currency field on POST /refunds, with the conversion handled on our side. ## Also noted during testing Partial refunds are rejected outright on some payment methods. A UPI payment returned PARTIAL_REFUND_NOT_ALLOWED ("Partial refunds are not allowed for this payment method").

Automatically Sync PPP-Adjusted Checkout Prices to Website Pricing Pages

My website displays one subscription price, but Dodo Checkout sometimes displays a different price because of country-based PPP adjustments.I'd love a way to automatically display the same PPP-adjusted prices on my website that customers will see at checkout.Ideally:Fetch the effective price using just a product ID and customer country.Automatically reflect the PPP configuration and localized pricing set in Dodo.Return the correct currency, discount, and subscription renewal price.Update website prices automatically whenever pricing settings change.Offer a simple frontend-friendly pricing widget or SDK without exposing private API keys.I noticed Dodo already has a Checkout Preview API. Does it support the PPP pricing configuration used at checkout, including country-based adjustments?If it doesn't, could you consider extending it or introducing a dedicated public pricing-display API?This would eliminate pricing mismatches, improve customer trust, and make Dodo much easier to integrate into SaaS pricing pages.Thanks!

Support Maldivian National ID Cards and Government-Issued Business Documents for Verification

Hello Dodo Payments Team,I would like to request additional identity verification options for individuals and registered businesses in the Maldives.Currently, Dodo Payments’ identity verification system, powered by Persona, requests a passport for verification. However, many Maldivian citizens do not possess passports because they do not travel internationally.In the Maldives, the government-issued National Identity Card is widely used as an official identification document for banking, business registration, and other government services.Unfortunately, attempting to use a valid Maldivian National ID card in the passport verification process results in failure.I would like to suggest the following improvements:1. Support Maldivian National ID CardsAllow Maldivian citizens to verify their identities using valid government-issued National ID cards.Provide National ID verification as an alternative to passport verification.2. Accept Government-Issued Business DocumentsAllow registered businesses and sole proprietors to submit official Business Registration Certificates.Accept Business Profile Sheets issued by the relevant Maldivian government ministry as supporting documentation for business verification.3. Introduce Alternative Verification MethodsProvide manual identity verification when automated verification cannot recognize valid government-issued documents.Allow additional supporting documents to be submitted securely when necessary.4. Improve Document SelectionAllow users to select from supported document types, such as National ID cards or passports.Avoid requiring passports when other government-issued identification documents can satisfy verification requirements.5. Provide Clear Country-Specific Verification RequirementsDisplay accepted identity documents for each supported country.Inform users about document requirements before they begin verification to prevent unnecessary failures.Why This Feature Is ImportantMany legitimate entrepreneurs and sole proprietors in the Maldives operate legally registered businesses without holding passports.Requiring passports for identity verification creates an unnecessary barrier for individuals who already possess valid government-issued National ID cards.Supporting Maldivian National ID cards and official business documents would improve accessibility for Maldivian merchants while maintaining appropriate security and compliance standards.Business registration certificates and business profile sheets could serve as supporting documents for business verification, alongside the personal identity checks required by Dodo Payments.I hope the Dodo Payments team will consider implementing these improvements to make the platform more accessible to merchants in the Maldives.Thank you for your consideration.

[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.)_

Meta Conversions API (server-side) integration

Request Add a Meta Conversions API option alongside the existing Meta Pixel integration, allowing Dodo Payments to send server-side Purchase events directly to Meta. The server-side event should include: - Purchase value - Currency - Content IDs - Payment ID as the event_id, allowing Meta to deduplicate it with the corresponding Pixel event - Customer email or other hashed customer identifiers where available Why it matters: Merchants scaling their Meta advertising need reliable server-side purchase data for accurate attribution and campaign optimization. Currently, merchants must build and host their own webhook handler for payment.succeeded to send these events through the Conversions API. Use case: A merchant using Hosted Checkout and static payment links may not have access to their own checkout page or backend to trigger server-side Meta events. Adding native Conversions API support would allow these merchants to send accurate Purchase events without maintaining their own infrastructure. This request was raised in support conversation #31245.

Feature Request — Automatic USD-to-Local-Currency Conversion for Payouts

Hi dodo team feature request I would like Dodo Payments to introduce an automatic currency conversion feature that allows merchants to receive international payments while automatically converting their earnings into their preferred local currency for payouts.How It Should WorkAccept payments in USD: Merchants can charge customers worldwide in US dollars or any currency.Choose a payout currency: During account setup, merchants select their preferred payout currency based on their country or personal preference, such as ZAR (South African Rand) for South Africa.Automatic currency conversion: Dodo Payments automatically converts eligible USD earnings into the selected payout currency.Local currency payouts: Merchants receive their deposits directly in their chosen currency through their supported payout method.Transparent exchange rates and fees: Merchants can view the applicable exchange rate, conversion fees, and estimated payout amount before their funds are deposited.Flexible currency settings: Merchants can change their preferred payout currency if they move countries or update their business requirements, subject to eligibility and account verification.ExampleA merchant in South Africa sells a SaaS subscription for $100 USD.Customer pays: $100 USD.Automatic conversion: USD is converted into ZAR using the applicable exchange rate.Merchant receives: The equivalent amount in South African Rand, minus any applicable fees.Result: The merchant can sell globally in USD without manually converting currencies or managing unnecessary conversion steps.Why This Feature MattersThis feature would make Dodo Payments more convenient for international SaaS founders, AI entrepreneurs, digital product creators, and other online businesses.Merchants could price their products globally in USD while receiving their earnings in a currency that works for their local banking system.The goal: Let merchants earn globally in Any currency and get paid locally in their preferred currency, automatically and transparently.

configurable retry frequency for subscription renewals

Current: merchants can only set the recovery window (1–30 days). The retry schedule is fixed at 12 h → 24 h → 48 h → 72 h…, which means 1 retry on day 1 and 2 by day 3. Request: let merchants set the retry frequency, or retry more often in the first few days (for example daily for days 1–4), especially for insufficient-funds declines. Why: insufficient-funds declines often clear within a few days, when the customer is paid or tops up. More frequent early retries would recover more of these payments before the subscription stays on hold.

allow verification cancellation

allow verification cancellation so mistakes can be edited and resubmitted - for example i realized after submitting i need to change the product webpage URL as the url added has no product info (beginner mistake)

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

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

Gross vs. Net Revenue Analytics

Currently, merchants can view monthly revenue only for the current month and previous month. Request to extend this so merchants can view gross revenue and net revenue for every month historically, with an easy month-by-month breakdown for tracking and comparison. Ideally, this historical monthly data should also be available through the API for custom reporting and analytics.

Checkout: no way to add a merchant's terms and conditions checkbox

A merchant needs buyers to accept their Terms of Service at checkout for compliance. They do not have a sign-up page yet. Tested custom_fields with field_type: 'boolean' and required: true: https://test.checkout.dodopayments.com/session/cks_0NpLCLvsRsg39wolF1Zs2 1. No clickable links in labels. Markdown, plain URLs and HTML all show as plain text. 2. "Required" does not force a tick. A boolean is a Yes/No toggle, so the buyer can leave it unticked and pay. It is recorded as tos_accepted: "false". 3. Checkout only shows Dodo's own Privacy and Buyer Terms. There is no option for the merchant's. For the purchase the buyer is buying from Dodo as MoR, and our Buyer Terms on checkout covers that. Their own Terms of Service is about using their product (licence, usage, data), which sits between them and their user, so it is better collected on their side. Slack thread: https://dodopayments.slack.com/archives/C0C62C5B34L/p1791520510777839

Allow customers to remove their only saved payment method from the Customer Portal

Problem: Currently, customers can remove a saved payment method when they have multiple payment methods saved. However, if a customer has only one saved card, the card cannot be removed from the Customer Portal. Requested Feature: Allow customers to remove their only saved card directly from the Customer Portal, provided there are no active payment or subscription dependencies requiring that card.

in table give select all or unselect check box to delete the discount codes

in tables should have the check box to select all do delete bulk or in the filtered rows to delete that helps to reduce the time.