# Stripe

With the Noloco **Stripe integration**, you can seamlessly bring your Stripe data—like Customers, Invoices, Subscriptions, Products, and Prices—into your Noloco app. Whether you're building an internal tool or a customer-facing portal, this guide will walk you through everything you need to get set up, customize your views, and make the most of your synced Stripe data.

### Getting Started

Before you begin, make sure you have:

* A **Stripe account**
* An existing **Noloco app** on the Pro plan or higher

{% hint style="success" %}
The Stripe integration is available on the Pro plan or higher
{% endhint %}

### **Step-by-Step Setup:**

1. **Go to the Data tab** of your Noloco app.
2. Click **+ New Source** and select **Stripe,** or click this link: <https://portals.noloco.io/~/_/setup/stripe>
3. Click **Connect with Stripe** to launch the OAuth flow.
4. Choose the Stripe account you want to connect and authorize access.
5. Noloco will:
   * Automatically create tables for each supported Stripe object.
   * Mirror the relationships between them (e.g. Customers → Subscriptions).
   * Use AI to generate initial views that fit seamlessly into your app.

Once complete, your Stripe data will be synced into Noloco and ready to use.

### Syncing

We keep your data **continuously up to date** using **Stripe webhooks**, meaning any changes in Stripe (like new invoices or customer updates) will be reflected in Noloco in near real-time—no manual syncing needed. [Learn more about Live syncing](https://guides.noloco.io/data-overview/syncing#live-syncing)

### Supported Stripe Objects

The following objects are synced as Noloco tables:

| Stripe Object     | Read / Write Support                                               |
| ----------------- | ------------------------------------------------------------------ |
| **Customers**     | Read + Write (most fields editable)                                |
| **Invoices**      | Read-only                                                          |
| **Subscriptions** | Mostly read-only (some editable fields like cancellation settings) |
| **Products**      | Read + Write                                                       |
| **Prices**        | Read-only                                                          |

**Relationships between tables are preserved**, just like in Stripe:

* Customers → Subscriptions, Invoices
* Subscriptions → Products, Prices
* Products → Prices

#### Editable Fields

Here are some common editable fields:

**Customers**

* Name
* Email
* Phone
* Address
* Description
* Balance
* Currency

**Subscriptions (Limited)**

* Cancel At
* Cancel At Period End
* Collection Method
* Days Until Due
* Trial End

**Products**

* Name
* Description
* Active status
* URL

Invoices and Prices are **fully read-only**, due to Stripe's restrictions and complexity.

### Customization in Noloco

You can fully tailor your Stripe data views just like any other data source:

* Change field labels and visibility
* Apply filters or grouping
* Add calculated fields (formulas, lookups, rollups)
* Customize layouts for internal dashboards or client portals

### Access Control

Use **Noloco's** [**permissions**](https://guides.noloco.io/users-and-permissions/user-roles-and-permissions) **engine** to control who can see or edit Stripe data:

* Show clients only their own invoices
* Limit finance data to specific roles
* Restrict editing of sensitive fields

### Example Use Cases

Here’s how teams are putting the Stripe integration to work:

* **Support Teams** – Access customer billing history and subscriptions without switching tools.
* **Finance Teams** – Build reports and dashboards on invoices and product revenue.
* **Client Portals** – Let customers log in and pay invoices directly.
* **Unified CRM** – Merge Stripe data with your CRM for a full view of each customer.

### FAQs

<details>

<summary><strong>Who can use the Stripe integration?</strong></summary>

It's available on the **Business** and **Enterprise** plans.

</details>

<details>

<summary><strong>Can I control who sees Stripe data?</strong></summary>

Yes—Noloco [permissions](https://guides.noloco.io/users-and-permissions/user-roles-and-permissions) work just like with any other data source.

</details>

<details>

<summary><strong>Can I update subscriptions?</strong></summary>

Not directly in Noloco. Subscriptions are mostly read-only. We provide **links back to Stripe** to manage them safely.

</details>

<details>

<summary><strong>What if I need more fields or objects?</strong></summary>

We’re actively expanding support based on user demand. Let us know what you need!

</details>

### Making Payments FAQ

<details>

<summary><strong>Can I collect payments through Noloco using the Stripe integration?</strong></summary>

**Not directly.** Noloco doesn’t currently support **native payment processing** within the app interface. However, the integration makes it **very easy to collect payments** by leveraging Stripe’s built-in invoice flow.

Each invoice synced into Noloco includes a **Hosted Invoice URL**—this is a secure Stripe-hosted page where your customers can view and pay their invoice.

You can use this URL to:

* Display a **"Pay Now" button** in your client portal
* Share payment links via custom views or email actions
* Embed the link in automations or workflows

</details>

<details>

<summary><strong>Can I collect payments through Noloco using the Stripe integration?</strong></summary>

Once the invoice is paid in Stripe, the **status will automatically update** in Noloco via live-sync—so you and your customers always have an up-to-date view.

{% hint style="info" %}
Combine invoice filtering with user permissions to ensure customers only see their own payment links.
{% endhint %}

</details>


---

# Agent Instructions: 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:

```
GET https://guides.noloco.io/data/stripe.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.