Stable coin payout

Please enable payout with stable coin, it is safe with privacy and fast enough

PayPal Payout

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.

Able to connect your own domain to Store Front

Able to connect your own domain to store.dodopayments.com

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

Allow bank account change button on Dashboard

Custom domain for customer portal

It will be good to have an option for custom domain for the customer portal.. e.g. billing.example.com etc.

Fixed per‑currency pricing (exact local amounts)

Description: We need the ability to set exact prices per local currency (e.g., 199.00 PLN, 49.00 SEK) instead of FX‑converted amounts from a base currency. Adaptive Currency always converts dynamically, which makes it impossible to guarantee marketing‑friendly prices across EU markets. This is critical for multi‑locale SaaS where advertised prices must exactly match what users are charged. Use case: EU SaaS with localized pricing pages and country‑specific price points. Expected behavior: Define fixed prices per currency (price overrides), or Create products directly in local currencies (PLN, SEK, etc.)

Option to switch account email address

Add an option to change the email address.

Cancellation Reasons in Customer Portal

Add the ability for customers to select cancellation reasons directly in the Dodo Payments customer portal for subscriptions.​ This feature would help merchants gather valuable churn insights without relying on custom implementations on their own platforms

Feature Request: Automated Revenue Splitting & Multi-Party Payouts

I would like to request a native "Revenue Split" feature that allows merchants to automatically route percentages of incoming revenue to different beneficiaries/accounts in real-time. As distributed teams and partnerships become the norm, manual reconciliation of revenue sharing is a major pain point. Instead of one merchant receiving 100% of the funds and then manually calculating and transferring cuts to partners or co-founders, the payment platform should handle this "at the source." Key Functionality Needed: Programmable Splits: The ability to set rules (e.g., 50% to Founder A, 50% to Founder B) that execute automatically upon transaction settlement. Partnership/Agency Support: Allow temporary or capped splits (e.g., an agency takes a 3% rev-share for 24 months). Transparency: All parties involved should have visibility into the transaction flow to ensure trust. Use Cases: Bootstrapped Co-founders: Two friends launching a SaaS want to split profit 50/50 without setting up complex payroll or manual monthly transfers. Strategic Partnerships: A creator or affiliate partners with a product for a specific campaign and receives an automatic % of the sales generated from that specific cohort. Agency Hybrid Models: Service providers (like dev shops) lowering upfront fees in exchange for a backend revenue share of the product they build.

Payout through stablecoins

Custom domain emails

Instead of sending emails to customers from dodo we could add/connect our domain for sending transactions emails

Variable Discount Rules for a Single Coupon Code

Problem Statement: The current coupon system only allows a single discount value (e.g., 15% off) to be applied per coupon code. To run a promotion with different discounts for different products, merchants must create and manage multiple separate codes. Example Scenario: For a "Summer Sale" with 20% off T-Shirts and 15% off Shorts, a merchant needs to create two distinct codes, like SUMMER20 and SUMMER15. Proposed Solution: The ability to create a single coupon code that applies different percentage discounts based on a set of conditional rules. This would allow merchants to define logic within one coupon. A potential implementation could allow a merchant to create a coupon like SUMMER24 and define rules such as: If product is in category "T-Shirts", apply a 20% discount. If product is in category "Shorts", apply a 15% discount. If product SKU is "HAT-123", apply a 10% discount. For all other products, apply no discount.

Referral Program Feature

Set up a referral program where customers receive a unique code to share with a friend for a discount. However, the code should only work for the referred customer, preventing misuse.

Customizable Transactional Emails (Branding + editable templates)

Allow merchants to change sender/branding and edit email templates (subject/body) for receipts, payment confirmations, and delivery emails.

Automatic Reminder Emails for Incomplete or Failed Payments

Hi Team, I’d like to request a feature that automatically sends reminder emails to users who attempted a payment but did not complete it. This includes scenarios where the payment failed, requires payment method, or requires customer action. It would be helpful to offer configuration options such as: Selecting which payment statuses should trigger a reminder Setting the delay (in days) before the reminder email is sent This small enhancement would improve recovery of incomplete payments and provide a smoother experience for users.

Email Marketing Through Dashboard

Allow merchants to create, manage, and send targeted email campaigns directly from the dashboard, helping to drive customer engagement and retention.

Add China specific payment methods

Pls add China specific payment methods like: 1. Alipay 2. WeChat Pay 3. UnionPay (China UnionPay) etc… This would make conversion rates better for China based customers. Thanks

Disable "Initiate Refund" button when refunded successfully

When a payment is already refunded, it's better to disable "Initiate Refund" button and also highlight such transaction somehow so it's easier to notice that sale. Sometimes the sale could be a problematic, so highlighting refunds will be good.

Allow a grace period after a subscription ends before revoking the user’s benefits

Add support to set country specific pricing

Having adaptive currency is nice but even nicer would be able to manually round/set prices for specific countries.

Apple Pay support in Meta (Facebook / Instagram) in-app browser on iOS

Apple Pay does not work when the checkout page is opened inside the Facebook or Instagram in-app browser on iOS. This is a critical issue, because a significant share of SaaS and subscription products rely on Meta Ads (Facebook / Instagram) as a primary acquisition channel on iOS. Steps to Reproduce Create a checkout URL using Dodo Payments Open this URL inside the Facebook or Instagram app on an iPhone (in-app browser) Attempt to pay using Apple Pay Apple Pay fails to work At the same time: Apple Pay works correctly when the same checkout URL is opened in Safari Apple Pay works for competitors using Paddle / Stripe in the same Facebook / Instagram in-app browser Expected Behavior Apple Pay should be available and functional when the checkout is opened inside Meta in-app browsers on iOS.

Add overlay checkout option for Store

Credit Based Billing System

Option for Prepaid billing using credits mechanism

Add overlay checkout on Store Front.

Same as the title.

[Feature Request] Hosted Invoice PDFs

As of today (31 Dec 2025), Dodo Payments does not provide us with any option for a hosted invoice PDF. As of now we get the contents of the PDF in the response which we can then stream to the user or save it in S3 and then provide them with a view url. It would be great if we can obtain a InvoiceUrl in the payment details itself. That way, we could paginate over payments for a given subscription without having to worry about handling invoice processing at our end. Else right now we hav to do something like this // Step 1: Get all the payments details iter := s.client.Payments.ListAutoPaging(ctx, dodopayments.PaymentListParams{ SubscriptionID: dodopayments.F(req.SubscriptionId), }) paymentInvoices := make([]*DodoPaymentsInvoiceDetails, 0) for iter.Next() { p := iter.Current() // FEATURE SUGGESTION => p.InvoiceUrl to be obtained here to skip all the rest of the processing given below pdf, err := s.client.Invoices.Payments.Get(ctx, p.PaymentID) if err != nil { goLibOtelLogger.Errorf(ctx, err, "error fetching invoice pdf for payment id %s: %v", p.PaymentID, err) paymentInvoice.ErrorFetching = true paymentInvoice.Invoice = nil paymentInvoices = append(paymentInvoices, paymentInvoice) continue } paymentInvoice.Invoice = pdf paymentInvoice.ErrorFetching = false paymentInvoices = append(paymentInvoices, paymentInvoice) } if err := iter.Err(); err != nil { return nil, err } // Step 2: Process paymentInvoices and upload to S3 I am looking forward to this feature. Please, please help implement this as soon as possible.

Abandoned Cart Recovery

When a user adds item to their cart but do not proceed with the transaction, automatically send emails to recover it. Platforms like LemonSqueezy handle this as following: https://docs.lemonsqueezy.com/help/online-store/abandoned-cart-emails

Multiple prices on a product

Add a feature to add multiple plans/prices to a single product.

Short, clean links for a product link

It could be checkout.dodopayments.com/buy/username/product-name - the current one is too long and doesn't allow for discount codes to be added.

Allow instant Withdrawal or Weekly payout

[Feature Request] Custom metadata argument in change plan request

Currently, the GO SDK or the APIs do not support passing any custom metadata when calling the change plan workflow. This becomes a problem in the following scenario. Step 1: I create a subscription Step 2: I update the subscription by calling Change Plan to include an add-on Step 3: I update the subscription again by calling Change Plan to include an add-on Step 4: I received one failure and one success webhook event Step 5: There is no way for me to tell which webhook event corresponds to which action in my system/application Ideally, in all the async systems, there must be a request id or some kind of identifier that can then be used when consuming the event asynchronously to tie back the output with the initial set of actions. Having the capability to pass metadata or generate the ID for actions that would then trigger corresponding webhook does help the systems to integrate more seamlessly

Localization for Checkout Page

Checkout page should support multiple languages for all displayed content, as it is essential for improving conversion rates, especially for non-English speaking customers.

Analytics for each product

I would like to know the traffic source of each product if possible, this helps me understand where my traffic is coming from and how many customers convert.

Change plan at the end of billing cycle

This is a highly requested feature. Many people have been asking for this - changing the plan at the end of the billing cycle.

Scheduled downgrade

We would like to be able to perform a scheduled downgrade when the customer is on Max plan and wants to switch to the Pro plan. Support answered in the chat that this functionality is not supported. Right now we have a custom process with the scheduled cloud functions doing this for us, but it would be great to handle this from your side and see it in the dashboard tab.