> For the complete documentation index, see [llms.txt](https://wimika.gitbook.io/wimika-partner-bank-api-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wimika.gitbook.io/wimika-partner-bank-api-documentation/welcome-to-wimika-partner-bank-api.md).

# Welcome to Wimika Partner Bank API

Welcome to the Wimika Partner Bank API – your gateway to seamless integration and enhanced protection for your consumer customer against cyber fraud. Our API empowers banks and digital financial service providers to embed MoneyGuard, Wimika's proactive cyber fraud protection solution, into their mobile apps, delivering a secure and reliable experience to their individual customers.&#x20;

With our robust SDK and APIs, you can leverage our advanced technology to detect and prevent cyber fraud incidents in real-time, ensuring the safety of the funds in your customer’s account. Join forces with Wimika and offer a comprehensive defence against cyber threats, building trust and confidence among your valued customers. Explore the possibilities of Wimika Partner Bank API and easily safeguard your digital financial ecosystem.

## Overview

This documentation provides detailed information on the required API integration for Wimika MoneyGuard SDK to integrate successfully with your application.

MoneyGuard, developed by Wimika, is a comprehensive and integrated cyber fraud protection product that proactively protects individual customers of banks and digital financial services from cyber fraud by combining the latest in predictive threat intelligence, advanced threat prevention, security awareness training, user behavioural analytics, and real-time cyber fraud risk assessment with residual risk transfer.

### Key Solutions

* **Proactive Risk Prevention**: Detecting and preventing malicious cyber activities to safeguard your customer’s device, applications, Wi-Fi connections, and identity.
* **Residual Risk Transfer**: Swift reimbursement for unauthorised transactions and conducting comprehensive cyber fraud investigations using advanced digital forensics and threat intelligence in the unlikely event of cyber fraud.
* **Analytics**: Utilising AI/ML, threat intelligence, and data analysis to proactively prevent our platform from cyber threats, ensuring ongoing security against TTPs, IoCs, IoTs, and exploits.

## Quick links

{% content-ref url="/pages/2qyGXe0mh7t3UyCRWVs6" %}
[API Reference](/wimika-partner-bank-api-documentation/api-reference/bank-account.md)
{% endcontent-ref %}

{% content-ref url="/pages/KQaVHhmnzl1nf6xROnrF" %}
[API changelog](/wimika-partner-bank-api-documentation/get-started/api-changelog.md)
{% endcontent-ref %}

## Get Started

We've put together some helpful guides to get set up with our product quickly and easily.

{% content-ref url="/pages/rTOuUeTYu49sNdyct98R" %}
[Getting Set Up](/wimika-partner-bank-api-documentation/get-started/getting-set-up.md)
{% endcontent-ref %}

{% content-ref url="/pages/G0m4mF4BAGa2bA2TWqbl" %}
[API Requirements](/wimika-partner-bank-api-documentation/get-started/api-requirements.md)
{% endcontent-ref %}

{% content-ref url="/pages/geY4qfRs50GYVBwhLbBw" %}
[Handling Errors](/wimika-partner-bank-api-documentation/get-started/handling-errors.md)
{% endcontent-ref %}

This API documentation serves as a comprehensive guide to assist you in integrating and leveraging the full potential of our API. It provides detailed information on endpoints, request/response structures, authentication, error handling, and more.

We highly recommend thoroughly reviewing the documentation and utilising the provided examples for smooth and efficient utilisation of the APIs.

If you have any questions or require further assistance, please don't hesitate to contact our support team at <support@wimika.ng>.

Happy coding! 😊


---

# 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://wimika.gitbook.io/wimika-partner-bank-api-documentation/welcome-to-wimika-partner-bank-api.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.
