> For the complete documentation index, see [llms.txt](https://features.scnd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://features.scnd.com/v2.0/dashboards/payments-dashboard/payments-dashboard-time-based-rendering-type.md).
# Payments dashboard (Time-Based rendering type)
{% hint style="info" %} Path: Dashboard > payments
{% endhint %}
* [Definition](#id-1.14.x-paymentsdashboard-basicsolution-definition)
* [Create a payment](#id-1.14.x-paymentsdashboard-basicsolution-createapayment)
* [Read a payment](#id-1.14.x-paymentsdashboard-basicsolution-readapayment)
* [Update a payment](#id-1.14.x-paymentsdashboard-basicsolution-updateapayment)
* [Delete a payment](#id-1.14.x-paymentsdashboard-basicsolution-deleteapayment)
* [Related resources](#id-1.14.x-paymentsdashboard-basicsolution-relatedresources)
## Definition
User payment history is displayed on the payment dashboard page. Users can also access invoices through this page.
**WHO CAN USE THIS FEATURE?**
**Switch users:** All logged-in users
**Non-Switch users:** All logged-in offerors
**Non-Switch users:** All logged-in askers
## Create a payment
As an asker, payments are made during the booking process.
As an offeror, payments are received once the service is done. A service is considered done depending on the platform’s configuration and parameters. However, by default, a payment is sent manually by authorized administrators through their dashboard. To learn more about how payments are sent by administrators, please refer to [\[1.13.X\] Payments management](https://second-documentation.atlassian.net/wiki/spaces/SCNDFD/pages/6956255449).
## Read a payment
According to their role, users can see all transactions made or received on this page. On switch platforms, both views are available via dedicated buttons located on the top right corner of the dashboard page.
Each transaction (figure 1) displays:
* “*No. Transaction*”: a unique transaction ID.
* “*No. Booking/ Quote*”: the related booking’s ID.
* “*Invoice date*”: invoice creation date.
* “*Payment type*”: type of payment (standard booking payment, refund due to cancellation, refund due to mediation).
* “*Total*”: The total amount paid or received.
* “*Invoice/receipt*” icon: transaction invoice download link.
{% hint style="info" %} This invoice concerned only the fees charged by the platform, it is not related to the service.
The offeror has to send himself the invoice of the service.
{% endhint %}
figure 1
## Update a payment
Users cannot update payments.
Askers can cancel a booking request which will automatically create a refund.
Users can open a mediation (if the bundle is enabled) to request administrator intervention and potentially have the administrator update the payment terms if deemed relevant and justified.
## Delete a payment
Users cannot delete payments.
Askers can cancel a booking request which will automatically create a refund.
Users can open a mediation (if the bundle is enabled) to request administrator intervention and potentially have the administrator update the payment terms if deemed relevant and justified.
## Related resources
**SBO:**
* [Payments management](https://second-documentation.atlassian.net/wiki/spaces/SCNDFD/pages/6956255449)
**Business rules:**
* [Payment Service Provider (PSP) - Business rules](https://second-documentation.atlassian.net/wiki/spaces/SCNDFD/pages/6956090933)
---
# 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://features.scnd.com/v2.0/dashboards/payments-dashboard/payments-dashboard-time-based-rendering-type.md?ask=&goal=
```
`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.