Chat Payment Widget

The Maven chat payment widget lets your chatbot or web app collect card payments without redirecting the customer, sending them to Stripe Checkout, or handling card data yourself. Drop in a <script> tag and a Maven.createPayment() call, and the customer enters their card into a secure iframe we host.

Inline in chat

Renders as a message in your chatbot UI. No redirects.

Secure by default

Card data never touches your servers — we handle tokenization and charging.

Any gateway

Stripe, Authorize.net, Braintree, Shift4, or Fiserv — same code.

	Widget	Voice
Customer experience	Types card into a form	Reads card aloud on a phone call
Best for	Chatbots, in-app checkout, support flows	IVR, phone support, outbound calls
Round-trip time	30-60s typical	60-90s typical
Customer effort	Low	Medium

You can use both on the same project — they share gateway connections, API keys, and webhook endpoints.

How it works

Your server creates a session

One POST /v1/widget-sessions call with your API key, the amount, and the gateway. You get back a session_id.

Your frontend mounts the widget

Include widget.js once, then Maven.createPayment({ sessionId }).mount("#slot") — the iframe appears inline in your chat UI.

Customer enters card details

The iframe is served from Maven’s domain. Card data goes directly from browser to Maven to VGS to the gateway.

Your callbacks fire

onSuccess({ transaction_id, card_brand, card_last4, ... }) or onFailure({ error_code, error_message }).

Webhook confirms (optional)

Same webhook format as voice — your server gets an authoritative notification even if the customer closes the tab.

Architecture

┌────────────────────────────────────────────────────┐
│  Your page (chatbot)                                │
│  ┌──────────────────────────────────────────────┐  │
│  │  <iframe src="api.trymaven.com/widget/..."> │  │  ← Maven hosts this
│  │    Secure Payment                            │  │
│  │    Card Number: ____________                 │  │
│  │    Expiry: __/__   CVV: ___                  │  │
│  │    [Confirm and Pay]                         │  │
│  │  </iframe>                                   │  │
│  └──────────────────────────────────────────────┘  │
│  ↑ Your page only gets onSuccess/onFailure         │
│    callbacks. Never sees card data.                │
└────────────────────────────────────────────────────┘
               ↓
        Maven → payment gateway

The card data path: browser → Maven iframe → Maven backend → gateway. Your page and server never touch raw card data.

Ready to integrate?

Quickstart

10-minute integration guide.

SDK Reference

Complete Maven.createPayment() API.

Customization

Theme, labels, fields, sizing.

Webhooks

Handle payment results server-side.

Inline in chat

Secure by default

Any gateway

​When to use the widget vs voice

​How it works

​Architecture

​Ready to integrate?