Connection 01
Separate production tenant
KC Washer Dryer Rentals operates as its own Rivet tenant with its own configuration and account relationships.
Customer proof
How KC Washer Dryer Rentals became Rivet’s real operating test bed.
KC Washer Dryer Rentals gave Rivet a real business with customers, inventory, payments, delivery work, and accounting requirements to test against.
What connects
Keep the information and the work in the same story.
Connection 02
Tenant-owned live Stripe account
The existing KC payment account was connected through Rivet rather than replaced by a shared platform account.
Connection 03
Accounting verification
A controlled live payment and refund were captured for supported LedgerLine delivery and idempotent replay verification.
How it works
A connected path with clear control points.
Each stage preserves the customer, rental, tenant, and operating context needed by the next one.
- 1
Separate the business from the platform
Treat KC Washer Dryer Rentals as a customer tenant rather than hard-coding its identity into Rivet.
- 2
Connect the tenant’s own payments
Authorize its existing Stripe account through the Rivet Connect production flow.
- 3
Run a controlled live transaction
Use a low-value payment and refund to verify the real tenant, account mapping, webhook, and invoice lifecycle.
- 4
Trace the accounting result
Capture the supported records for LedgerLine and verify that replaying the same source does not duplicate the economic event.
Operational outcomes
Make the next action easier to see.
01
A verified tenant boundary
The KC company’s settings, account identifiers, payments, and accounting scope remain distinct from Rivet and other tenants.
02
A production payment path
The tenant can receive a supported live card payment in its own connected Stripe account.
03
A reusable onboarding model
The same controlled approach can onboard another real tenant without importing KC-specific business rules.
Questions
What buyers usually need to know.
1
Is KC Washer Dryer Rentals the Rivet platform account?
No. It is a separate rental-business tenant using Rivet.
2
Did Rivet replace the KC Stripe account?
No. The existing eligible Stripe account was connected to its Rivet tenant.
3
Was the accounting path tested with real money?
A controlled low-value live payment and refund were used to verify the production path.
4
Does every new tenant inherit KC pricing and rules?
No. Each tenant must configure or migrate its own products, prices, requirements, locations, and policies.
This case study describes controlled production verification. It does not publish customer card data, private credentials, or confidential tenant records.
Keep exploring