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

# Native wallet integration

We want to ensure a seamless payment and connection experience for users, regardless of the platform they are coming from.

Our website fully supports standard [EIP-1193](https://eips.ethereum.org/EIPS/eip-1193) Ethereum provider injection. This means if your mobile application (via WebView) or browser extension injects a standard provider into `window.ethereum`, your users can immediately interact with our dApp without any additional configuration.

### Partner UI customization

While standard injection works out-of-the-box, we offer an enhanced integration tier for our partners.

We understand the value of brand consistency. When a user accesses our site specifically through your application's WebView, a generic "Connect Wallet" button may not feel like a native part of the experience.

To solve this, we support UI injection customization. By adding a specific, pre-agreed property (flag) to your injected `window.ethereum` object, our frontend can detect your specific environment.

When detected, we can replace standard buttons like "Connect Wallet" with a customized button tailored to your brand — using your name, logo, and color palette.

**Example**

Instead of a generic connect button, a user opening our site inside the "Trust Wallet" app could see a branded experience like the one below:

<figure><img src="https://1912462442-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPgl1t8uCisy0T57qHG35%2Fuploads%2Fe4V3xGQyu8tz55lNBCin%2Fimage.png?alt=media&#x26;token=4368585b-cd3f-4a84-86d8-e6d09f7d6763" alt=""><figcaption></figcaption></figure>

### How to get started

If you are a wallet provider or have an app with an embedded crypto browser and want to provide this native feel for your users:

1. Contact us: reach out to our partnerships team at <hello@fonbnk.com>.
2. Define the flag: we will agree on a unique string identifier to look for on the `window.ethereum` object (e.g. `window.ethereum.isAlphaWallet = true`).
3. Provide assets: send us your preferred button label text, hex colour codes, and SVG logo icon.

We will handle the implementation on our end to ensure your users feel right at home when transacting on our platform.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fonbnk.com/widget-integration/native-wallet-integration.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 `automate deployments from our CI pipeline` 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.