Connection 01
Stripe Connect
Each tenant can connect its eligible Stripe account for renter card payments, payout control, and supported refunds.
Rivet integrations
Rivet keeps customer operations as the source of context while specialized services handle payment processing and accounting.
What connects
Connection 01
Each tenant can connect its eligible Stripe account for renter card payments, payout control, and supported refunds.
Connection 02
Supported payment and refund records can be captured and delivered with tenant and transaction identity intact.
Connection 03
Connections, credentials, payments, and accounting records stay scoped to the rental company they belong to.
How it works
Each stage preserves the customer, rental, tenant, and operating context needed by the next one.
Establish the rental company and its tenant-scoped operating settings.
Complete Stripe’s hosted account connection and capability checks for that tenant.
Eligible production workspaces can use Rivet-managed LedgerLine setup rather than requiring renters to connect accounting themselves.
Capture payment and refund events, deliver supported accounting records, and use idempotency to prevent duplicate replay.
Operational outcomes
01
The tenant owns its payment account while Rivet coordinates the workflow.
02
Payment, refund, and accounting references can be followed back to the rental source.
03
Supported accounting delivery uses stable identities so a replay does not create a second economic event.
Questions
No. Each rental company connects its own eligible Stripe account to its Rivet tenant.
No. LedgerLine is an accounting connection for the rental company. Supported provisioning and delivery are managed through Rivet.
Yes. LedgerLine is optional and does not control whether the tenant can accept supported Stripe payments.
Supported deliveries use idempotent references so retrying the same record can be verified without duplicating it.
Keep exploring