One click on an order raises a Stripe checkout page and hands you the link. When the buyer pays, the payment lands on that exact order — no reconciliation, no copying amounts between two systems.
24 h
the longest a checkout page can live
Stripe is the default way to accept a card almost everywhere in Europe, and this adapter connects it to the one place your team already works. The CRM asks Stripe for a hosted Checkout Session, so the buyer enters their card on Stripe's own page — no card number, CVV or token ever reaches Obriym, and your PCI surface does not change. The result comes back as a signed webhook, and the CRM verifies that signature before it believes a single figure.
Open the order, go to the Payments tab and press “Payment link”. Choose the amount — the full total or a deposit — and how long the buyer has to pay.
The CRM gives you the link and sends nothing itself. Email it, paste it into a messenger thread, or read it out — the choice of channel stays yours.
Stripe reports the result to the CRM directly. The payment is attached to the order it was raised from, the order's paid total updates, and your team sees it without opening the Stripe Dashboard.
Every other payment provider here lets you pick a term up to 30 days. Stripe does not, and the CRM would rather show you fewer options than a deadline the checkout page will not honour.
Every notification is checked against Stripe's signature over the exact bytes received, inside a five-minute replay window. An unsigned or altered notification is refused outright — never logged as a warning that still moves a payment.
Some payment methods clear hours after the buyer leaves the page. The CRM waits for the outcome instead of marking an order paid off a bank debit that has not settled.
If your WooCommerce or Shopify shop already charges through the same Stripe account, those payments arrive as well. Each one is matched to its order where possible, and anything unmatched waits in the Payments journal to be linked by hand — never silently dropped.
Each request carries the reservation's own idempotency key, so a double-click or a retried submit produces one checkout page, not two.
Stated up front, because the honest limits of an integration matter more than its feature list.
The adapter is in beta: it is complete and you can connect it today — the keys come from your own Stripe Dashboard, with no review or approval to wait for. What has not happened yet is a real payment through it on a live merchant account, which is the only thing that earns the “available” badge here. Stripe also does not onboard businesses in every country, so check that yours is supported before connecting.
Connect Stripe once, then raise a link from any order without leaving the CRM.
Start for free