> For the complete documentation index, see [llms.txt](https://docs.stammer.ai/stammer.ai-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stammer.ai/stammer.ai-docs/support/faq/alternatives-to-stripe-connect.md).

# Alternatives to Stripe Connect

### 1. **Manual Fulfillment**

This method is ideal for agencies with the following characteristics:

* Use a payment processor other than Stripe.
* Are unable to use Stripe for billing.
* Prefer off-platform billing.
* Require a manual or "Done For You" (DFY) offer.
* Opt for unlimited usage by bypassing sub-account billing.

#### Steps:

1. Manually create a sub-account in your Stammer.ai admin dashboard.
2. Customize the account settings to align with your client's needs.
3. Handle billing and payment processing outside the platform.

<figure><img src="/files/bLk3c9P7B97gbovpVYeT" alt=""><figcaption></figcaption></figure>

***

### 2. **Automatic Fulfillment (Stripe Integration) (Most Popular)**

This is the most common and scalable method, designed for agencies that:

* Use Stripe as their payment processor.
* Require unlimited scaling to sell Stammer.ai solutions as their own SaaS.
* Prefer a DIY (Do It Yourself) approach for fully self-serve account management.

#### Features:

* Enables seamless integration of subscription packages directly into your SaaS.
* Allows clients to subscribe and manage billing directly through Stripe.

#### Steps:

1. Configure subscription packages in your Stammer.ai dashboard.
2. Connect your Stripe account for automatic payment processing.
3. Clients can select and subscribe to packages directly through your platform.

<figure><img src="/files/AlOFnuJsmfy4LWlDHUPb" alt=""><figcaption></figcaption></figure>

***

### 3. **Automatic Fulfillment (API Integration)**

This method applies to agencies that:

* Use a different payment processor other than Stripe.
* Cannot use Stripe for billing.
* Prefer off-platform billing.
* Need manual or DFY offers.
* Require unlimited usage by bypassing sub-account billing.

#### Features:

* Uses API integrations to automate account creation and management.
* Compatible with platforms like PayPal and Zapier for payment and webhook automation.

{% content-ref url="/pages/PYyFnIQTDgcXD0PL2Dhp" %}
[API Documentation](/stammer.ai-docs/white-label/white-label-api/api-documentation.md)
{% endcontent-ref %}

#### Steps:

1. Use the API to connect your payment processor or webhook service.
2. Automate account creation and billing events through tools like Zapier.
3. Handle client subscriptions and payments through your chosen platform.

<figure><img src="/files/SiegmwCidk9287rrpaOE" alt=""><figcaption></figcaption></figure>

#### Choosing the Right Method

Select the fulfillment method based on your agency's payment processor, scalability requirements, and operational preferences. If you're unsure which method is best for your setup, our support team is here to help.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.stammer.ai/stammer.ai-docs/support/faq/alternatives-to-stripe-connect.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.