Additional payment methodsPublic preview

To accept non-card payment methods through the QR code interface, create a PaymentIntent and include your preferred payment method types in the payment_method_types parameter.

• To present your customer all payment method options in the checkout flow, combine card_present with non-card payment method types. We recommend enabling this if you operate in a heavily offline environment because only cards are supported in offline mode.
• If you dont want to accept cards, support only non-card payment method types.
• If you know which payment method you want to direct your customer to checkout to, select a single payment method type.

Capture type

Not all payment methods support manual capture. The following table shows which payment methods support manual capture:

To support the broadest set of payment methods, create your PaymentIntent with capture_method set to automatic. To support manual capture for card payments and Affirm while also accepting payment methods that require automatic capture, set capture_method on the nested payment_method_options.card_present attribute to manual.

curl https://api.stripe.com/v1/payment_intents \
  -u "sk_test_wU7nrJCZspk1NPDxiQgAF05q:" \
  -d amount=1000 \
  -d currency=usd \
  -d "payment_method_types[]=card_present" \
  -d "payment_method_types[]=wechat_pay" \
  -d capture_method=automatic \
  -d "payment_method_options[card_present][capture_method]=manual"

Unlike card payments, processing QR code payments occurs asynchronously. When processing a PaymentIntent with a QR code payment method, Stripe generates a QR code unique to that payment.

After processing the payment, the reader displays the QR code for the customer to scan with their mobile device. Shortly after the customer completes the payment on their device, the reader updates to reflect the completed payment.

QR code payments support both processing the payment immediately and the two-step collect-and-confirm flow.

curl https://api.stripe.com/v1/terminal/readers/tmr_xxx/process_payment_intent \
  -u "sk_test_wU7nrJCZspk1NPDxiQgAF05q:" \
  -d payment_intent=pi_xxx \
  --data-urlencode "process_config[return_url]=https://my.store.com/payment-completed"

curl https://api.stripe.com/v1/terminal/readers/tmr_xxx \
  -u "sk_test_wU7nrJCZspk1NPDxiQgAF05q:"

{
  "id": "tmr_xxx",
  "object": "terminal.reader",
  ...
  "status": "online",
  "action": {
    "type": "process_payment_intent",
    "process_payment_intent": {
      "payment_intent": "pi_xxx"
    },
    "status": "in_progress",
    "failure_code": null,
    "failure_message": null
  }
}

Free up the reader to take another payment

It might take multiple minutes for a customer to complete the payment on their device. Instead of waiting for the reader to reflect the result of the completed payment, you can free up the reader to take a payment for a different customer.

After the customer scans the QR code and switches to their device to complete the payment, use the cancel_action endpoint to reset the reader.

curl -X POST https://api.stripe.com/v1/terminal/readers/tmr_xxx/cancel_action \
  -u "sk_test_wU7nrJCZspk1NPDxiQgAF05q:"

After you cancel the readers action to process the payment, the payment intent remains in the requires_action state, allowing the customer to complete the payment. Use the payment_intent.succeeded and payment_intent.payment_failed webhooks to reconcile the result of the completed payment. Learn how to monitor a PaymentIntent with webhooks.