React Native implementation for Stripe.js Checkout.

The library allows you to use Stripe.js Checkout with react-native without ejecting. You can use it with both server-side implementations and client-side implementations. Simply ensure you follow the url structure guidelines below.
Ensure you've completed the setps in prequisites.
Install package via npm or yarn:
npm install --save react-native-stripe-checkout-webview OR yarn add react-native-stripe-checkout-webview
import StripeCheckout from 'react-native-stripe-checkout-webview';
import StripeCheckout from 'react-native-stripe-checkout-webview';
type Props = { STRIPE_PUBLIC_KEY: string, CHECKOUT_SESSION_ID: string };
const MyStripeCheckout = ({ STRIPE_PUBLIC_KEY, CHECKOUT_SESSION_ID }: Props) => (
<StripeCheckout
stripePublicKey={STRIPE_PUBLIC_KEY}
checkoutSessionInput={{
sessionId: CHECKOUT_SESSION_ID,
}}
onSuccess={({ checkoutSessionId }) => {
console.log(`Stripe checkout session succeeded. session id: ${checkoutSessionId}.`);
}}
onCancel={() => {
console.log(`Stripe checkout session cancelled.`);
}}
/>
);
export default MyStripeCheckout;
?sc_checkout=success&sc_sid={CHECKOUT_SESSION_ID}?sc_checkout=cancelurlJoin(mySuccessUrl, '?sc_checkout=success&sc_sid={CHECKOUT_SESSION_ID}').stripePublicKey (String) - Stripe public key of your project.checkoutSessionInput (Object) - Object to be passed to Stripe's redirectToCheckout function. Docs.js
// Server-side Checkout Session flow
{
sessionId: string,
// optional client-side locale hint - see "A note on locale" below
locale?: string,
}
// Client-only flow
| {
clientReferenceId: string,
successUrl: string,
cancelUrl: string,
items?: Array<{ plan: string, quantity: string }>,
lineItems?: Array<{ price: number, quantity: number }>,
mode?: 'payment' | 'subscription',
submitType?: string,
// common
customerEmail?: string,
billingAddressCollection?: 'required' | 'auto',
shippingAddressCollection?: {
allowedCountries: Array<string>,
},
locale?: string,
}sessionId, only sessionId is forwarded to Stripe's redirectToCheckout. Stripe.js rejects the call if any other field (successUrl, cancelUrl, locale, ...) is passed alongside sessionId, which would prevent Checkout from loading. Configure those options when you create the Checkout Session server-side instead.onSuccess (?Function) - Called upon success of the checkout session with { ...props, checkoutSessionId: 'CHECKOUT_SESSION_ID' }onCancel (?Function) - Called upon cancellation of the checkout session with { ...props }onLoadingComplete (?Function) - Called when the Stripe checkout session webpage loads successfully.options (?Object) - custom options to display content in the webviewhtmlContentLoading (String) - Html string to display a loading indication. - default: <h1 id="sc-loading">Loading...</h1> - note: The loading item is set on the element with id='sc-loading'htmlContentError (String) - Html string to display stripe errors. - default: `- note: The error is set on the element with id='sc-error-message'
-htmlContentHead(String) - Html string to inject in head. - default: ''
-webViewProps(?Object) - WebView Component props, spread on the WebView Component.
-renderOnComplete` (?(props) => React$Node) - Optional rendering function returning a component to display upon checkout completion. note: You don't need this if your onSuccess and onCancel functions navigate away from the component.
lineItems/items): pass locale directly in checkoutSessionInput - it is forwarded to redirectToCheckout.sessionId): the displayed language is determined by the locale you set when creating the Checkout Session server-side - this is the authoritative source. Stripe.js does not accept locale alongside sessionId, so it is not forwarded to redirectToCheckout (doing so would prevent Checkout from loading). As a convenience, a locale passed in checkoutSessionInput is still applied as a client-side hint via the Stripe.js constructor (Stripe(key, { locale })), which localizes error strings.successUrl/cancelUrl redirect via the WebView's onShouldStartLoadWithRequest and prevents the WebView from navigating to it, then calls onSuccess/onCancel. This means your successUrl/cancelUrl can be a placeholder that does not resolve to a real page - the WebView will never render its (potentially 404) content. Just make sure the URLs follow the structure above.WKUserScript *script = [[WKUserScript alloc] initWithSource:html5HistoryAPIShimSource injectionTime:WKUserScriptInjectionTimeAtDocumentStart
forMainFrameOnly:YES];
// [wkWebViewConfig.userContentController addUserScript:script]; // this line that inject "html5HistoryAPIShimSource" on startPull requests are highly appreciated! For major changes, please open an issue first to discuss what you would like to change.
$ claude mcp add react-native-stripe-checkout-webview \
-- python -m otcore.mcp_server <graph>