Stripe

Stripe integration in Rib has two separate layers:

• Workspace connector policy controls whether Stripe work is allowed.
• Builder Payments stores and validates the project owner's Stripe keys for one generated app.

This separation keeps payment governance clear and keeps Rib out of your app's funds flow.

Stripe connector policy

The Stripe connector is a governance layer.

It can control whether the agent may work with payment capabilities such as:

• Reading account status.
• Reading configured product and price status.
• Creating checkout sessions.
• Managing subscriptions.
• Issuing refunds.
• Handling disputes.
• Reading payment summaries.
• Managing webhooks.

Workspace owners and admins can manage these policies. A project can inherit workspace defaults or use a project-specific override when available.

Start selling with Stripe

First, create the product or subscription you want to sell in Stripe. Stripe will give each price an ID that starts with price_.

Then finish the setup in your project:

1. Open the Payments tab in Builder.
2. Choose Test and add your test keys.
3. Paste the Stripe Price ID for each product or subscription your app should sell.
4. Copy the webhook URL shown in Builder and add it to your Stripe webhook settings.
5. Paste the webhook signing secret from Stripe back into Builder Payments.
6. Repeat those steps under Live when you are ready to accept real payments.
7. Ask the agent to add the payment or subscription experience to your app.

Only the prices you add in Builder Payments can be sold by the app. Customers can buy one-time products without creating an account, while subscriptions require them to sign in.

Test and Live stay saved separately. Builder Preview automatically uses Test, while your published app automatically uses Live. Adding Live settings does not remove the Test setup, so you can keep testing future changes safely. Success and cancel destinations must stay within your app origin.

Payment status

A project may show statuses such as:

• Not configured.
• Missing required secrets.
• Test mode configured.
• Live mode configured.
• Validation failed.

Treat test mode as a validation environment. Do not publish a real checkout flow until your team has confirmed the correct mode, products, prices, webhook endpoint, and legal/payment responsibilities.

What Rib does not do

Rib does not:

• Create Stripe seller accounts for your app.
• Operate your app as a Stripe platform flow.
• Collect application fees on payments your app accepts.
• Store payment keys in the workspace connector policy.

Copyable prompt

Add subscription payments to my app. Customers should sign in before subscribing and see a clear confirmation when payment succeeds.

That is enough. The agent already knows how to use the Stripe setup from your project, so you do not need to mention APIs, files, or technical implementation details.

Next steps

• Control payment permissions: Connectors
• Publish safely: Publish your project
• Review prompt safety: Prompting best practices