BankOpenAPI

com.bankopenapiPublished by bankopenapi.comOfficial publisherv1.0.0Updated Nov 7, 2026

Accept bank transfers in Vietnam: VietQR payment requests, payment status, incoming transactions.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote MCP server for BankOpenAPI that lets an assistant create VietQR payment requests and check payment status and incoming bank transfers in Vietnam.

What you can do
  • Create VietQR payment requests to accept bank transfers
  • Check the status of a payment request
  • Retrieve incoming transactions
  • No individual tools are listed in the manifest, so exact operations are not documented here.
When to use it
Useful when you want an assistant to handle Vietnamese bank-transfer collection: issuing VietQR payment requests, following up on whether a payment has arrived, and reviewing incoming transactions.
Requirements
Remote streamable HTTP endpoint at app.bankopenapi.com. Requires a BankOpenAPI API key sent in the Authorization header; live keys and test (Sandbox) keys are issued from the provider's dashboard. Network access to the provider is needed.
Before you install
The API key is a secret sent in the Authorization header and grants access to payment operations; keep it out of logs and shared transcripts. Creating payment requests and reading transaction data affect real money flows and financial records, so verify amounts and recipients. Test with a Sandbox key before using a live key.

Installation

In SourceWeft

  1. Open BankOpenAPI in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.bankopenapi%2Fbankopenapi/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "bankopenapi": {
      "type": "http",
      "url": "https://app.bankopenapi.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestNov 7, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.