> ## Documentation Index
> Fetch the complete documentation index at: https://docs.assistable.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Stripe for client rebilling

> Connect the agency payment account and verify the customer before accepting client wallet payments.

Your connected Stripe account supports client wallet funding for rebilling. It is distinct from the payment method you use to pay Assistable.

## Connect

1. Open **Rebilling** in the intended workspace.
2. Select **Connect to Stripe** and complete Stripe authorization for the agency account that should receive client payments.
3. Return to Rebilling and inspect the connected account identity. If the connection check fails, retry it before configuring clients.
4. Open the client's **Configure rebilling → Customer** panel. Review an existing customer, or use the options below to create or link one in this connected account. Verify its identity before using it.
5. Review the intended client's saved usage categories and prices in **Configure rebilling**, then test its [wallet payment flow](/v3/guides/billing/client-wallet).

## Customer panel options

Use a customer in the connected agency Stripe account. Linking a customer does not charge them.

| Option or status | Meaning |
| - | - |
| Not linked | No customer is currently saved for this client account |
| Create Stripe customer | Creates and saves a customer using this account's contact details |
| Link existing customer | Opens the **Stripe customer ID** field; enter the intended `cus_…` identifier |
| Verify and link | Checks the entered customer against the connected Stripe account and saves the link immediately |
| Linked | A customer ID is saved; use **Verify connection** to check it |
| Verified | The customer connection was checked successfully in this dialog |
| Change | Opens the customer-ID editor for a different customer |
| Cancel | Discards the unsaved customer-ID edit |

If multiple Stripe connections are recorded and the panel cannot choose one, customer creation is unavailable. Verify an existing customer to identify the matching connection. A new-card wallet payment can also create or repair the customer's mapping, so manually creating a customer is not required for every client.

## Check before disconnecting

Disconnecting requires workspace Owner or Admin access and clears the workspace's stored Stripe connection. It is not a customer/payment-method migration between Stripe accounts. Review affected client collection before changing payment accounts.

To disconnect intentionally, use **Disconnect Stripe** in Rebilling and review **Disconnect Stripe?** before confirming. Reconnect the intended account afterward and review client customer mappings before accepting another payment. A previously saved customer ID may belong to the former Stripe account.

## Troubleshooting

If the authorization page does not open, check browser popup handling and retry from Rebilling. If access is restricted, use a workspace Owner or Admin. If a client customer cannot be verified, confirm the selected Stripe account and customer rather than repeatedly generating IDs.

A connection success message does not prove a client payment completed. Verify the payment result and wallet transaction for your controlled test. See [client wallet funding](/v3/guides/billing/client-wallet) and [billing records](/v3/guides/billing/review-activity).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.