# Vision

In the digital era, despite the increased transaction speed and efficiency, cryptocurrencies have yet to achieve mass adoption in seemingly ideal areas such as peer-to-peer payments, e-commerce transactions, and cross-border remittances. We believe that ease of use and the lack of a recourse mechanism in dispute resolution are significant barriers preventing cryptocurrency payments from becoming the method of choice for mainstream transactions.

In traditional financial systems, entities like banks and payment processors such as PayPal act as centralized dispute managers. These institutions have managed to convince users that credit cards are preferable to cash for most transactions by offering robust mechanisms to contest charges and resolve disputes. This assurance of dispute resolution significantly contributes to user trust, particularly in unfamiliar or new transaction environments, thereby enhancing wider payment adoption.

FrogPay is designed to bridge this gap in the cryptocurrency ecosystem. By integrating account abstraction and decentralized dispute resolution, FrogPay aims to instill a higher level of confidence among users in their transactions with others. Cryptocurrency payments are inherently irreversible; typically, the only recourse for a refund depends on the goodwill of the recipient, and an addressing error can result in permanent loss of funds. FrogPay addresses these challenges by introducing a revolutionary protocol that not only enhances security but also ensures that users have a dependable mechanism to manage disputes effectively.

<br>


---

# 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://frogpay.gitbook.io/whitepaper/introduction/vision.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.