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

# Platform payments

> Manage payment connections and understand the limits of the available tests, products, and reports.

## Summary

Doglytdc Payments brings together platform connections, credentials, and preferences.
It is separate from Connect and from your DoglyTdc subscription status.
Parts of this interface still use demonstration results.

> [!WARNING]
>
> The connection test runs locally: it checks fields and formats without contacting the provider.
> A success message does not prove external authentication or receipt of payment.
> Reports display fixed zeros, and product creation simulates synchronization.

## Who it is for

* People organizing payment platforms in the dashboard.
* People updating credentials or choosing a default platform.
* Anyone who needs to distinguish saved settings from a verified integration.

## How to open

Open the platform payments area in the dashboard.
The `?tab=platform-payments` entry opens `payments:overview`.
Internal screens use `payments:` followed by the screen identifier.

## Screens and features

![Screenshot: Platform payments](https://mintcdn.com/dogly-tdc/qOnot79kPtISSKbW/images/doglytdc/platform-payments.png?fit=max\&auto=format\&n=qOnot79kPtISSKbW\&q=85\&s=a821ff1834315b5edb96445db30f6f08)

Platform payments in DoglyTdc

### Overview

In `overview`, review connected, active, and available platforms.
You can enable or disable connections, choose a default, edit credentials, and disconnect.
The product counter is fixed at zero in this implementation.

### Analytics

In `analytics`, the active platform count comes from saved connections.
Conversion, paid contracts, average order value, and revenue per platform use fixed zeros.
The chart is a placeholder; these values are not an actual financial report.

### Connect

In `connect`, choose a listed platform and enter the requested credentials.
The form offers test mode where available for the selected platform.
Saving a connection does not prove the provider accepted its credentials.

**1. Add the connection**

Choose a platform and complete its required fields.
Check the selected mode before saving.

**2. Review the settings**

Check the active status, default platform, and saved credentials.
Treat the test only as a local check of required fields and formats.

**3. Verify beyond the local test**

Review the setup with the provider before relying on the connection.
Do not treat visual confirmation as proof of payment.

### Products

In `products`, open the creation form and enter a name, price, and other available options.
The flow simulates delays and per-platform results, including example identifiers.
It does not create real products with providers or populate a persistent catalog on this screen.

### Settings

In `settings`, notification and synchronization controls are available.
Notifications change only in the screen's local state; this flow does not save those preferences.
Synchronization controls likewise do not establish that an automatic process is running.
Disconnecting all platforms requires confirmation.

### Transactions

In `transactions`, revenue and transaction totals are fixed at zero.
The screen displays an empty state without querying transaction history.
The search field is not connected to a real list in this implementation.

### Webhooks

In `webhooks`, generate and copy the URL shown for each connection.
The generated URL can be saved in the connection settings.
The configured label indicates a saved URL, not confirmed event delivery.
Set up the provider too; copying the address does not complete that step.

## Credits and limits

DoglyTdc credit balance and subscription status appear in separate payment components.
Do not confuse that balance with customer revenue or the zeros in these reports.
This connections area does not itself confirm a credit purchase or change your plan.

## Permissions

Managing connections requires an authenticated dashboard session.
Enter credentials only in the appropriate fields and do not share them in documents.
Check the platform before editing it or confirming a disconnection.

## Common errors

| Message | What it means | What to do |
| - | - | - |
| Required fields | Required form information is missing. | Complete the selected platform's fields. |
| Connection failed | The local check found an issue. | Review the credential fields and formats. |
| Enter name and price | The product form is incomplete. | Complete the fields, remembering that synchronization is simulated. |
| No transactions yet | The implemented screen displays an empty state. | Do not use this screen to conclude there were no external sales. |

## Frequently asked questions

> [accordion] Does the test confirm provider access?
>
> No. It runs locally and does not contact the provider.

> [accordion] Do reports represent my receipts?
>
> Not in this implementation. They contain fixed zeros and placeholders alongside real connection counts.

> [accordion] Does creating a product publish a real offer?
>
> Not in this flow. Synchronization and its results are simulated.
> See Connect for the specific Cakto and Kiwify features.

## Related

> [card] [Connect](https://docs.doglytdc.dev/en/doglytdc/business/connect.md)

> [card] [Metrics](https://docs.doglytdc.dev/en/doglytdc/business/metrics.md)


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