> For the complete documentation index, see [llms.txt](https://developer.prophius.com/developer-console/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.prophius.com/developer-console/documentation.md).

# Documentation

**Welcome to the Prophius Developer Hub! 🚀**

Hey there!

First off, a big virtual high-five for hopping on board! We're stoked to have you here and you're in for quite an adventure.

Now, you might be wondering, "What’s Prophius all about?" Think of us as your toolbox, filled to the brim with all the cutting-edge payment tools you need to create something epic. Our mission? To help you seamlessly integrate your awesome creations with the Prophius ecosystem starting with turning mobile phones into payment terminals. 

Here's the cool part: we've tried to make this console as jargon-free and friendly as possible. Because let's face it, while we all enjoy a good brain teaser, nobody wants to sift through a thick fog of technical gibberish, right? 😉

**A Sneak Peek of What's Inside:**

* **Mobile SDK:** Its straightforward, you'll have them up and running quickly
* **Backend APIs:** Ready to supercharge your apps? The APIs are waiting to be your best friends.
* **Code Samples:** Because we know a little inspiration can lead to some next-level innovation.
* **Community & Support:** A space for you to chat, share, learn, and brainstorm with fellow Prophius enthusiasts.

But enough chit-chat! Dive right in, explore, experiment, and let your creativity run wild. And hey, if you get stuck or just fancy a chat about all things tech, give us a shout. We're always around.

Cheers to the beginning of a rad tech journey together! 🎉

Happy coding, The Prophius Squad 🤓

{% embed url="<https://youtu.be/Gd3OiwDLGog>" %}

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td></td><td><strong>PayContactless</strong></td><td>Make and Receive contactless payments on your mobile device without any extra hardware or terminal.</td><td><a href="https://3209134532-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcLvbYKDk7En5o0Lfwh2V%2Fuploads%2FgZJAfstrZWo2mFVe8Q1R%2F62ac62921e0914058b6efa6f_TTP%20Web.png?alt=media&amp;token=74544ca1-cd41-4ead-8b64-7bbfda8fd797">62ac62921e0914058b6efa6f_TTP Web.png</a></td><td><a href="/developer-console/paycontactless.md">PayContactless</a></td></tr></tbody></table>


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://developer.prophius.com/developer-console/documentation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

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.