Feature Requests
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

8 Comments

Sign in to comment

HC
HS C·24 days ago

We strongly support this request. We operate SAJU-K (https://saju-k.com), a low-priced, one-time AI-assisted digital entertainment service with no physical delivery and no mandatory account signup.

A separate name/email/address form before payment-method selection is a blocker for us. If this mandatory manual personal-information step remains, we cannot use Dodo Payments as the checkout solution for our service. Reducing address fields or embedding the same form does not solve the problem.

This is not unique to SAJU-K: the same flow creates a major adoption barrier for other low-priced digital-content businesses, one-off AI services, and guest-checkout merchants. Asking buyers to complete a form before they can even choose an already-configured wallet undermines the main benefit of express payments and risks abandonment on small purchases.

Required flow:

1. Show eligible wallets and card options immediately.

2. Let Apple Pay/Google Pay users authorize in the wallet, collecting required receipt/tax information from it where supported, without a separate merchant-side form.

3. For card payments, request only information genuinely required for that method and country. We are not asking to bypass tax or authentication requirements or to use fabricated identities.

We also found a reproducible sandbox error on October 10, 2026 (JPY 199 and USD 1.99). POST /checkouts accepts feature_flags.single_page=true with minimal_address=true, but the hosted page still renders the contact form. Continue calls /api/checkout/sessions/{id}/confirm, which returns HTTP 403 with: "Single-page checkout sessions confirm through prepare-confirm". Setting single_page=false works, but wallets are still behind the contact form.

Trying confirm=true without customer information instead returns 422 requiring an existing customer_id or a new customer's name and email. We do not have those details before a guest purchase.

Can you provide a working payment-method-first integration, enable any available beta for our account, and clarify the timeline? Please also investigate the single_page error. This is a core usability requirement for our service and a commercially important issue for other digital merchants, not just a cosmetic preference.

C
Chess1475·3 months ago

I agree. great suggestion.

TT
Tensor Tonic·3 months ago

Any updates on this?

T
Trixon·3 months ago

they said it's now planned about a month ago

KD
Krishna Dheer·4 months ago

Ks payment

DD
Deep Doshi·7 months ago

Hi Zac, thanks for sharing. We are currently reviewing this feature request and will share an update by the end of next week on the same

FI
featurebase import·7 months ago

hi Deep, any updates? seems like it’s a long week

Z
Zac·8 months ago

why is nothing happening guys?