Embedded
Payment UI in an iframe on your domain. checkout/create with ui_mode: embedded.
Developer sandbox · RapidCents checkout
Test checkout session APIs and real integration flows—without shipping a storefront first.
This app calls RapidCents only from the server: OAuth, checkout/create, RapidPay, and webhooks. Use it to validate behavior before you wire the same patterns into production.
checkout/create
v1/checkout-pay
Webhooks
OAuth · bearer
What you can exercise here
-
1
Embedded & hosted — same API, different
ui_mode; iframe vs full-page redirect. - 2 RapidPay — compact one-time flow and optional in-cart modal.
- 3 Subscriptions — recurring plans via checkout where your integration requires it.
Not a production storefront—reference wiring you can copy into your own stack.
Integration reference, not a marketing site
- Secrets and tokens stay on the server; the browser never holds your API bearer.
- Cart and checkout mirror how a real app would call RapidCents—inspect requests in your logs.
- Webhook endpoint and admin views help you confirm events end-to-end.
- Docs pages map each mode to routes, payloads, and example code in this repo.
Three integration modes
Same RapidCents account and session concepts—different UX. Pick the mode that fits your product, then use the docs for request shapes and callbacks.
Hosted
Full-page redirect to RapidCents. Same API with ui_mode: hosted.
RapidPay (quick payment)
Quick payment—one-time flow via v1/checkout-pay. Typical UX: modal, iframe, or new window (cart demo uses an in-page modal; standalone rapid form also available).
How it works
A short path from sample catalog through checkout—mirroring a typical integration.
-
01
Add products
Use the sample catalog to build a cart—line items and totals match what you’d send in
Products →checkout/create. -
02
Open checkout
From the cart, pick embedded, hosted, or RapidPay—this app posts to your backend, which calls RapidCents.
Cart → -
03
Pay (test cards)
Complete payment in the iframe, redirect, or modal. Exercise success, cancel, and error paths.
-
04
Confirm on server
After return URLs or UI events, verify payment and order state on your backend per RapidCents guidance before fulfillment.
Success & cancel →
Request flow (summary)
Your production app should follow the same boundaries: browser talks only to your server; your server holds OAuth and calls RapidCents.
┌─────────────┐ HTTPS ┌──────────────────┐ OAuth / API ┌─────────────┐
│ Browser │ ────────────▶ │ This Laravel app │ ─────────────────▶ │ RapidCents │
│ (no token) │ ◀──────────── │ (bearer + create)│ ◀───────────────── │ gateway │
└─────────────┘ HTML/JSON └─────────┬────────┘ checkout_url └──────┬──────┘
│ │
│ POST /webhooks/payment │
│◀────────────────────────────────────┘
▼
Verify signature · update order stateDiagram is simplified; see documentation for headers, payloads, and iframe postMessage handling.
Documentation
Endpoint reference, parameter tables, and code excerpts aligned with this codebase—start with the overview, then dive into embedded, hosted, or RapidPay.
Sample catalog
Add items and run any checkout mode from the cart—fastest way to test end-to-end.
No image
Adipisci quod quis
Vel sed amet fugit deleniti et sit itaque sequi excepturi.
$5.00 CAD
No image
Enim eos at
Sed quos nulla nihil est maxime laboriosam natus est fuga nam quia cum quo tempore tenetur.
$3.50 CAD
No image
Est illum et
Provident rerum doloremque non dolore voluptas nihil qui et voluptate quam minus culpa maiores.
$1.99 CAD
No image
Harum laborum et
Neque provident officia culpa atque cumque sit ut.
$3.99 CAD
No image
Nam quod enim
Quisquam reiciendis est vel officia aut corrupti nam sunt rerum natus enim placeat ullam nihil dolorem.
$4.00 CAD
No image
Numquam odit sunt
Aliquid necessitatibus commodi est est sint mollitia quo nam voluptas animi voluptatum.
$8.00 CAD
No image
Velit quo animi
Rerum dolor et libero animi sunt non ex.
$9.99 CAD
No image
Vero ipsam ipsam
Ducimus laudantium et et et consequuntur numquam quasi et ullam quam assumenda distinctio cumque.
$3.90 CAD