Migrate payment methods to the Dashboard

Turn on different Checkout payment methods through the Dashboard.

Migrate your Checkout payment methods to Dashboard settings by following this guide. By changing your integration to pull your payment method preferences from the Dashboard, Stripe displays all compatible payment methods to your customers when checking out depending on the chosen currency or any payment method restrictions like maximum transaction amounts. Stripe also presents the most relevant payment methods for each customer based on their location and currency used. The checkout page prioritizes showing payment methods known to increase conversion for your customer’s location while lower priority payment methods are hidden beneath an overflow menu.

Your customers see multiple payment methods at check out that are popular for their location and currency. But, they still have the option to choose a different payment method from the overflow menu.

Update your integration

If you have an existing integration with Stripe Checkout, you must change one line of code in your integration to begin migrating payment methods to the Dashboard.

Upgrading your integration initially turns off any non-default payment methods for your integration, like bank redirects. If you added payment methods to your Checkout integration, you must go to the payment methods settings page in the Dashboard to turn them back on.

Previously, you used the payment_method_types parameter when defining your Checkout session to accept different payment methods. To begin managing your payment methods in the Dashboard, remove this parameter from your integration.

After you remove the payment_method_types parameter from your integration, some payment methods turn on automatically including cards and wallets. The currency parameter restricts the payment methods that are shown to the customer during the checkout session.

Stripe::Checkout::Session.create({
mode: 'payment',
# Remove the payment_method_types parameter
# to manage payment methods in the Dashboard
payment_method_types: ['card'],
line_items: [{
  price_data: {
  # The currency parameter determines which
  # payment methods are used in the Checkout Session.
    currency: 'eur',
      product_data: {
        name: 'T-shirt',
      },
      unit_amount: 2000,
    },
    quantity: 1,
  }],
  success_url: 'https://example.com/success',
  cancel_url: 'https://example.com/cancel',
})

View available payment methods in the Dashboard

View your payment methods settings to see the payment methods that you currently accept. This list includes the payment methods turned on by default, like cards. These payment methods cost the same or less than cards and settle immediately.

Add or remove payment methods to your integration

On the payment methods settings Dashboard page, you can view the available payment methods and turn on new payment methods for your integration.

You can enable some payment methods just by selecting Turn on. However, some payment methods require additional steps to turn them on. For those cases, you’ll see a button that says Set up or Review terms.

To learn more about which payment methods are right for your business, see our payment methods guide.

(Recommended) Handle delayed notification payment methods

Depending on the type of payment method you integrate, there can be a 2-14 day delay in payment confirmation. If you set up webhooks to automatically fulfill orders with your Checkout integration, when you add your first delayed notification payment methods, you need to update your code.

This step is only required if you plan to use any of the following payment methods: Bacs Direct Debit, Bank transfers, Boleto, Canadian pre-authorized debits, Konbini, OXXO, SEPA Direct Debit, SOFORT, or ACH Direct Debit.

When receiving payments with a delayed notification payment method, funds aren’t immediately available. It can take multiple days for funds to process so you should delay order fulfillment until the funds are available in your account. After the payment succeeds, the underlying PaymentIntent status changes from processing to succeeded.

You’ll need to handle the following Checkout events:

Event Name	Description	Next steps
checkout.session.completed	The customer has successfully authorized the debit payment by submitting the Checkout form.	Wait for the payment to succeed or fail.
checkout.session.async_payment_succeeded	The customer’s payment succeeded.	Fulfill the purchased goods or services.
checkout.session.async_payment_failed	The payment was declined, or failed for some other reason.	Contact the customer via email and request that they place a new order.

These events all include the Checkout Session object.

Update your event handler to fulfill the order:

# Set your secret key. Remember to switch to your live secret key in production.
# See your keys here: https://dashboard.stripe.com/apikeys
Stripe.api_key = 'sk_test_4eC39HqLyjWDarjtT1zdp7dc'

# You can find your endpoint's secret in the output of the `stripe listen`
# command you ran earlier
endpoint_secret = 'whsec_...'

post '/webhook' do
  event = nil

  # Verify webhook signature and extract the event
  # See https://stripe.com/docs/webhooks/signatures for more information.
  begin
    sig_header = request.env['HTTP_STRIPE_SIGNATURE']
    payload = request.body.read
    event = Stripe::Webhook.construct_event(payload, sig_header, endpoint_secret)
  rescue JSON::ParserError => e
    # Invalid payload
    return status 400
  rescue Stripe::SignatureVerificationError => e
    # Invalid signature
    return status 400
  end

  case event['type']
  if event['type'] == 'checkout.session.completed'
    checkout_session = event['data']['object']

    fulfill_order(checkout_session)
  end
  when 'checkout.session.completed'
    checkout_session = event['data']['object']

    # Save an order in your database, marked as 'awaiting payment'
    create_order(checkout_session)

    # Check if the order is already paid (for example, from a card payment)
    #
    # A delayed notification payment will have an `unpaid` status, as
    # you're still waiting for funds to be transferred from the customer's
    # account.
    if checkout_session.payment_status == 'paid'
      fulfill_order(checkout_session)
    end
  when 'checkout.session.async_payment_succeeded'
    checkout_session = event['data']['object']

    # Fulfill the purchase...
    fulfill_order(checkout_session)
  when 'checkout.session.async_payment_failed'
    session = event['data']['object']

    # Send an email to the customer asking them to retry their order
    email_customer_about_failed_payment(checkout_session)
  end

  status 200
end

def fulfill_order(checkout_session)
  # TODO: fill in with your own logic
  puts "Fulfilling order for #{checkout_session.inspect}"
end

def create_order(checkout_session)
  # TODO: fill in with your own logic
  puts "Creating order for #{checkout_session.inspect}"
end

def email_customer_about_failed_payment(checkout_session)
  # TODO: fill in with your own logic
  puts "Emailing customer about payment failure for: #{checkout_session.inspect}"
end

Testing

Ensure that stripe listen is still running. Go through Checkout as a test user, like you did in the prior steps. Your event handler should receive a checkout.session.completed event, and you should have successfully handled it.

Now that you’ve completed these steps, you’re ready to go live in production whenever you decide to do so.

Test your integration

Use test payment details and the test redirect page to verify your integration. Click the tabs below to view details for each payment method.

Payment method	Scenario	How to test
Credit card	The card payment succeeds and doesn’t require authentication.	Fill out the credit card form using the credit card number `4242 4242 4242 4242` with any expiration, CVC, and postal code.
Credit card	The card payment requires authentication.	Fill out the credit card form using the credit card number `4000 0025 0000 3155` with any expiration, CVC, and postal code.
Credit card	The card is declined with a decline code like `insufficient_funds`.	Fill out the credit card form using the credit card number `4000 0000 0000 9995` with any expiration, CVC, and postal code.