Skip to main content
The Stripe hosted payment page sends the buyer to a Stripe Checkout Session hosted by Stripe, where they pay with Stripe Link or any other payment method you have enabled. Unlike Onelink, which renders the Stripe Payment Element on a Gr4vy-hosted page, nothing is rendered or confirmed on a Gr4vy surface: Stripe owns the whole payment page. By default the page offers card and Stripe Link. Stripe Link recognizes a returning buyer by their email address and lets them check out with saved details.

Setup

Follow the Stripe setup instructions before configuring the hosted payment page. After setting up your Stripe account, make sure card payments, Stripe Link, and any other payment methods you intend to offer are enabled in Stripe. For shared APM credentials and payment IDs, see Stripe APM credentials.

Configuration

Payment method types

The Payment method types credential controls which methods Stripe offers on the Checkout page. Set it to a comma-separated list, for example card, link, paypal. Leave it blank to offer card and Link.
Stripe rejects a Checkout Session that offers Link on its own, so card is always included alongside link. If the list contains a value that is not recognized, the connector falls back to card and Link rather than sending something Stripe would reject.

Capabilities

Supported countries

Supported currencies

Webhooks

The buyer completes the payment on Stripe’s page, so webhooks must be configured to keep the status of transactions in sync. Webhooks are configured in the Stripe Dashboard within Developer Settings under Webhooks. This connector relies on the following Stripe webhooks:
  • payment_intent.canceled
  • charge.expired
  • charge.refund.updated
  • charge.refunded
  • payment_intent.succeeded
  • payment_intent.amount_capturable_updated
  • payment_intent.payment_failed

Limitations

  • No stored payment methods - The connector does not tokenize or store payment methods, so it cannot be used for recurring payments. Use Card via Stripe for stored credentials and merchant-initiated transactions.
  • Full captures only - Partial capture is not supported. Refunds, including partial refunds, are supported.
  • Popup required - The redirect opens in a popup rather than an inline frame, because Stripe’s Checkout page cannot be embedded.

Integration

The integration is a redirect to the Stripe-hosted Checkout page. Start by creating a new transaction with the following required fields.
After the transaction is created, the API response includes payment_method.approval_url and the buyer_approval_pending status.
Send the buyer to the approval_url to complete the payment on Stripe’s page. After they finish, Stripe returns them to the redirect_url you provided when creating the transaction and Gr4vy checks the payment intent behind the Checkout Session. Do not rely solely on the redirect - either poll the transaction or (recommended) rely on webhooks to detect the final status (for example capture_succeeded or failure states). For mobile, use your app deep link for redirect_url (for example, yourapp://).

Testing

Stripe has instructions on how to test payments, including the test cards to use on the Checkout page.