Migrate payment methods to the Dashboard

For existing Stripe Checkout integrations that specify payment_method_types, you must remove this parameter to migrate payment methods preferences to the Dashboard. After you remove the parameter from your integration, some payment methods turn on automatically including cards and wallets. The currency parameter restricts the payment methods the customer sees in the Checkout Session.

$stripe->checkout->sessions->create([
  'line_items' => [
    [
      'price_data' => [
        'currency' => 'eur',
        'product_data' => ['name' => 'T-shirt'],
        'unit_amount' => 2000,
      ],
      'quantity' => 1,
    ],
  ],
  'mode' => 'payment',
  // Remove the payment_method_types parameter to manage payment methods in the Dashboard
  'payment_method_types' => ['card'],
  'success_url' => 'https://example.com/success',
]);

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.

Payment methods

By default, Stripe enables cards and other common payment methods. You can turn individual payment methods on or off in the Stripe Dashboard. In Checkout, Stripe evaluates the currency and any restrictions, then dynamically presents the supported payment methods to the customer.

To see how your payment methods appear to customers, enter a transaction ID or set an order amount and currency in the Dashboard.

You can enable Apple Pay and Google Pay in your payment methods settings. By default, Apple Pay is enabled and Google Pay is disabled. However, in some cases Stripe filters them out even when they’re enabled. We filter Google Pay if you enable automatic tax without collecting a shipping address.

Checkout’s Stripe-hosted pages don’t need integration changes to enable Apple Pay or Google Pay. Stripe handles these payments the same way as other card payments.

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.

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 might need to update your code.

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:

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\Stripe::setApiKey(
'sk_test_4eC39HqLyjWDarjtT1zdp7dc');

// You can find your endpoint's secret in your webhook settings
$endpoint_secret = 'whsec_...';

$payload = @file_get_contents('php://input');
$sig_header = $_SERVER['HTTP_STRIPE_SIGNATURE'];
$event = null;

try {
  $event = \Stripe\Webhook::constructEvent(
    $payload, $sig_header, $endpoint_secret
  );
} catch(\UnexpectedValueException $e) {
  // Invalid payload
  http_response_code(400);
  exit();
} catch(\Stripe\Exception\SignatureVerificationException $e) {
  // Invalid signature
  http_response_code(400);
  exit();
}

function fulfill_order($session) {
  // TODO: fill me in
  error_log("Fulfilling order...");
  error_log($session);
}

function create_order($session) {
  // TODO fill me in
}

function email_customer_about_failed_payment($session) {
  // TODO fill me in
}

// Handle the checkout.session.completed event
if ($event->type == 'checkout.session.completed') {
  $session = $event->data->object;

  // Fulfill the purchase...
  fulfill_order($session);
}
switch ($event->type) {
  case 'checkout.session.completed':
    $session = $event->data->object;

    // Save an order in your database, marked as 'awaiting payment'
    create_order($session);

    // Check if the order is 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 ($session->payment_status == 'paid') {
      // Fulfill the purchase
      fulfill_order($session);
    }

    break;

  case 'checkout.session.async_payment_succeeded':
    $session = $event->data->object;

    // Fulfill the purchase
    fulfill_order($session);

    break;

  case '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($session);

    break;
}

http_response_code(200);

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.

See Testing for additional information to test your integration.