- Create a hosted Checkout Session straight from an Iris payment record; the customer pays on Stripe's page
- Status sync and refunds from Iris; webhooks (Stripe-Signature, 5-minute tolerance) reconciled on a schedule
- SAQ-A by design: raw-card endpoints (/v1/tokens, /v1/payment_methods) are excluded from the catalogue
- Live or test mode chosen by the key prefix (sk_live_ / sk_test_) — same connection, same base URL
- 585 catalogued routes (262 read-only): customers, invoices, subscriptions, payouts, balance, disputes and more, tryable from the hub
Stripe API Connector
Collect payments from Apivom Iris with Stripe's hosted Checkout: a payment record becomes a Checkout Session, the customer pays on Stripe's page, status and refunds sync back, and signed webhooks are reconciled by scheduled automation — your own secret key, no card data through Apivom.
What you can do
Use cases
- Send a pay link from the deal — Create the Checkout Session from the payment record attached to an opportunity or invoice and share Stripe's hosted page; the record updates itself when the customer pays.
- Refund without leaving the CRM — Issue full or partial refunds on a settled payment from Iris and let the webhook reconcile the final state and the Stripe fee.
- Test the whole flow before going live — Connect a test key first, run real Checkout Sessions with Stripe test cards and switch to the live key when accounting signs off — nothing else changes.
Stripe's REST API is the de-facto standard for online payments: payment intents, Checkout Sessions, customers, invoices, subscriptions, refunds, payouts and the balance behind them. Apivom Iris uses it as a payment gateway for the money side of the CRM. From a payment record an operator creates a hosted Checkout Session; the customer completes the payment on Stripe's own page, so no card number ever touches Apivom and the integration stays in the lightest PCI scope (SAQ-A) — the catalogue deliberately omits Stripe's raw-card endpoints. Stripe's webhooks arrive at a per-tenant receiver, are verified with the endpoint signing secret within a five-minute tolerance and reconciled by scheduled automation, so status changes and refunds show up on the payment record without polling. Live and test are the same connection: the key prefix decides. Beyond the checkout flow, any of the 585 catalogued routes can be run by an administrator from the Iris integrations hub against the stored key, with every call logged in your tenant.
Your Stripe secret key (sk_live_… or sk_test_…) sent as Bearer per request; mode follows the prefix. The optional webhook signing secret (whsec_…) is used only by Iris to verify Stripe-Signature on inbound events. Both are encrypted in your Iris tenant; Apivom Atlas stores nothing.
Frequently asked questions
Does any card data pass through Apivom?
No. Payments are collected on Stripe's hosted Checkout page, and the catalogue excludes the endpoints that would accept raw card numbers (POST /v1/tokens, /v1/payment_methods). Apivom only ever sees Stripe's object ids and statuses.
How are webhooks secured and what happens if one is missed?
Each tenant has its own receiver URL; Stripe's Stripe-Signature header is verified with your endpoint's signing secret (HMAC-SHA256 over the raw body, 5-minute tolerance). Events are stored and reconciled by scheduled automation, so a delayed or retried event is applied once, in order.
Can I use Stripe objects other than Checkout from Iris?
Yes — customers, invoices, subscriptions, payouts, balance transactions and the rest of the 585 catalogued routes can be called by an administrator from the integrations hub (reads directly, writes behind a confirmation). Automated workflows exist today for Checkout Sessions, status sync, refunds and webhooks.
Does Apivom charge per API call for this connector?
No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.
Where are my credentials stored and who can see the traffic?
Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.
More Atlas integrations
AI integration guide (llms.txt)
Machine-readable markdown — feed it to your AI assistant as integration instructions.