# Using a Third-Party Payment Provider

Onside offers the flexibility for you to use your own existing payment processing infrastructure instead of our integrated Payment SDK. This guide outlines the responsibilities and technical requirements for this option.

{% hint style="warning" %}
This option is intended for developers with specific business needs and an existing, robust payment system. It involves a higher commission rate and mandatory technical integration for reporting. For most developers, using the integrated [**Onside Payment SDK**](https://app.gitbook.com/s/ar2Jh3wLmverIdTKRpUi/payment-sdk/welcome) is the more straightforward and profitable choice.
{% endhint %}

***

### Developer Responsibilities

If you choose to process payments using your own provider (e.g., Stripe, Adyen, PayPal), you are responsible for:

* **All Payment Processing:** Handling the entire transaction lifecycle, including charging the user, processing refunds, and managing subscription billing logic.
* **Security & Compliance:** Ensuring your payment flow is secure and compliant with all relevant regulations (like PCI DSS).
* **Customer Support:** Providing direct support to users for any payment-related issues.
* **Mandatory Transaction Reporting:** Reporting every successful transaction from Onside users back to us via our API.

***

### Mandatory Transaction Reporting

To ensure accurate commission calculation and platform accounting, you **must** report every successful purchase or subscription renewal made by users who downloaded your app from Onside.

This is done programmatically via our dedicated [**Transaction Reporting API**](https://app.gitbook.com/s/vu6GnA9QIMP7iX7RdyRJ/transactions-reporting-api).

Failure to report transactions accurately and in a timely manner is a violation of the Onside Developer Agreement and may result in the removal of your app from the marketplace.

***

### Commission Structure

Using a third-party payment provider is subject to a **different commission model** than our standard integrated SDK. The commission rate will be higher to account for the use of the platform and our role in app discovery and distribution.

The specific terms will be outlined in your Onside Developer Agreement or discussed with you directly. Please contact our developer support team for 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://docs.onside.io/console/monetization/using-a-third-party-payment-provider.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.