Xfers

Xfers is a Southeast Asian payments infrastructure company founded in Singapore in 2015 and backed by 500 Global, providing bank-transfer collection, payouts, escrow-style wallets, and lending disbursement APIs across Singapore and Indonesia. Xfers merged with Payfazz in 2022 to form the Fazz Financial Group, with its regulated Singapore dollar stablecoin and payments business continuing as StraitsX; the Xfers v3 API documentation for Singapore and Indonesia remains published at docs.xfers.io.

Xfers publishes 20 API contracts indexed on the APIs.io network, including Bank Account API, Charge API, Convenience Store Transfers API, and 17 more. Tagged areas include Payments, Fintech, Bank Transfers, Digital Wallet, and Lending.

The Xfers catalog on APIs.io includes 1 Spectral governance ruleset.

Xfers’ developer surface includes authentication, documentation, API reference, support, and 8 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

30.3/100 thin ▬ flat Agent 33/100 agent ready Heartbeat 33/100 slowing Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

4 published contracts

Payments Fintech Bank Transfers Digital Wallet Lending Singapore Indonesia Southeast Asia

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Application Identity & Verification

AE-160

ESignature

POST /v3/esignatures_registration POST /v3/esignatures_upload_document

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 30.3/100 · thin

Contract Quality 9.5 / 19

Developer Ergonomics 3.9 / 15

Access Clarity 0.0 / 15

Operational Transparency 1.8 / 10

Contract Governance 1.2 / 9

Discoverability 5.4 / 8

Regulatory Posture 2.1 / 15

Create-or-Update Ergonomics 2.8 / 10

Agent readiness — 33/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/xfers/"><img src="https://apis.io/badge/xfers/card.svg" alt="Xfers on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

8 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 0.0 — up to +20.0 composite points
Developer Ergonomics scores 26.2 — up to +14.8 composite points
Contract Quality scores 50.6 — up to +12.4 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/xfers/apis.yml: open an issue on github.com/api-evangelist/xfers to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Gulf and Southeast Asia Open Finance	regulated	28.8 (thin)	-	1
Southeast Asia and National Fintech Registers (Taiwan, UAE, Malaysia remittance, Indonesia SNAP)	regulated	28.8 (thin)	-	1
Consumer Lending Licensing (UK, US, Canada credit licence registers)	regulated	28.8 (thin)	-	1

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 20

Individual APIs this provider publishes, each with its own machine-readable definition.

Xfers Bank Account API

API to manage Bank Account

Xfers Charge API

API for Charges

Xfers Convenience Store Transfers API

The Convenience Store Transfers API from Xfers — 1 operation(s) for convenience store transfers.

Xfers Cutting Edge API

The cutting_edge API from Xfers — 2 operation(s) for cutting_edge.

Xfers Direct Bank Transfer Payments API

The Direct Bank Transfer Payments API from Xfers — 1 operation(s) for direct bank transfer payments.

Xfers Disbursements API

API for Disbursement

Xfers Fixed Virtual Account Bank Transfers API

The Fixed Virtual Account Bank Transfers API from Xfers — 2 operation(s) for fixed virtual account bank transfers.

Xfers Intents API

**For user case 1:** When a user is performing a top-up via [GET /transfer_info](http://docs.xfers.io/#get-transfer-info), they might forget to enter their contact number which ...

Xfers Loans API

Loans Management

Xfers Modify Payments API

The Modify Payments API from Xfers — 1 operation(s) for modify payments.

Xfers Payment Queries API

The Payment Queries API from Xfers — 1 operation(s) for payment queries.

Xfers Payment Queries (Hide first) API

The Payment Queries (Hide first) API from Xfers — 1 operation(s) for payment queries (hide first).

Xfers Payout API

API for Payout

Xfers Registration API

Xfers Repayments API

API for Repayment

Xfers Testing API

API for testing purposes

Xfers Unique Amount Bank Transfers API

The Unique Amount Bank Transfers API from Xfers — 1 operation(s) for unique amount bank transfers.

Xfers User Account API

Manage User and Accounts

Xfers Withdraw API

API for Withdrawal

Xfers E Signature API

API for e-signature

Scroll for all 20

Open Collections 20

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Xfers Bank Account API

OPEN COLLECTION

Xfers Bank Account Charge API

OPEN COLLECTION

Xfers Bank Account Convenience Store Transfers API

OPEN COLLECTION

Xfers Bank Account cutting_edge API

OPEN COLLECTION

Xfers Bank Account Direct Bank Transfer Payments API

OPEN COLLECTION

Xfers Bank Account Disbursements API

OPEN COLLECTION

Xfers Bank Account E-signature API

OPEN COLLECTION

Xfers Bank Account Fixed Virtual Account Bank Transfers API

OPEN COLLECTION

Xfers Bank Account Intents API

OPEN COLLECTION

Xfers Bank Account Loans API

OPEN COLLECTION

Xfers Bank Account Modify Payments API

OPEN COLLECTION

Xfers Bank Account Payment Queries API

OPEN COLLECTION

Xfers Bank Account Payment Queries (Hide first) API

OPEN COLLECTION

Xfers Bank Account Payout API

OPEN COLLECTION

Xfers Bank Account Registration API

OPEN COLLECTION

Xfers Bank Account Repayments API

OPEN COLLECTION

Xfers Bank Account Testing API

OPEN COLLECTION

Xfers Bank Account Unique Amount Bank Transfers API

OPEN COLLECTION

Xfers Bank Account User Account API

OPEN COLLECTION

Xfers Bank Account Withdraw API

OPEN COLLECTION

Scroll for all 20

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Xfers API Rules

64 rules · 51 errors 8 warnings 5 info

SPECTRAL

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Xfers Authentication

apiKey/http · 4 schemes

SECURITY

Xfers Domain Security

TLSv1.3 · DNSSEC · DMARC

SECURITY

Resources

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Postman

Postman

Postman

Postman

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 2

Status, limits, changes, and where to get help

StatusPage

StatusPage

Support

Support

Company 1

The organization behind the API

Website

Website

Other 1

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Source (apis.yml)

aid: xfers
name: Xfers
description: Xfers is a Southeast Asian payments infrastructure company founded in Singapore in 2015 and backed by 500 Global,
  providing bank-transfer collection, payouts, escrow-style wallets, and lending disbursement APIs across Singapore and Indonesia.
  Xfers merged with Payfazz in 2022 to form the Fazz Financial Group, with its regulated Singapore dollar stablecoin and payments
  business continuing as StraitsX; the Xfers v3 API documentation for Singapore and Indonesia remains published at docs.xfers.io.
url: https://raw.githubusercontent.com/api-evangelist/xfers/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- 500-global
x-successors:
- name: Fazz
  url: https://fazz.com
- name: StraitsX
  url: https://www.straitsx.com
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: true
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - openapi
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
image: https://docs.xfers.io/Xfers_X_Blue_Small.png
tags:
- Payments
- Fintech
- Bank Transfers
- Digital Wallet
- Lending
- Singapore
- Indonesia
- Southeast Asia
tags_raw:
- Payments
- Fintech
- Bank Transfers
- Digital Wallets
- Lending
- Singapore
- Indonesia
- Southeast Asia
apis:
- aid: xfers:xfers-bank-account-api
  name: Xfers Bank Account API
  description: API to manage Bank Account
  humanURL: https://docs.xfers.io/Singapore
  baseURL: https://www.xfers.io/api
  tags:
  - Bank Account
  properties:
  - type: OpenAPI
    url: openapi/xfers-bank-account-api-openapi.yml
  - type: Documentation
    url: https://docs.xfers.io/Singapore
  - type: Documentation
    url: https://docs.xfers.io/V3/Indonesia
  - type: Documentation
    url: https://docs.xfers.io/indonesia/payment-gateway
- aid: xfers:xfers-charge-api
  name: Xfers Charge API
  description: API for Charges
  humanURL: https://docs.xfers.io/Singapore
  baseURL: https://www.xfers.io/api
  tags:
  - Charge
  properties:
  - type: OpenAPI
    url: openapi/xfers-charge-api-openapi.yml
  - type: Documentation
    url: https://docs.xfers.io/Singapore
  - type: Documentation
    url: https://docs.xfers.io/V3/Indonesia
  - type: Documentation
    url: https://docs.xfers.io/indonesia/payment-gateway
- aid: xfers:xfers-convenience-store-transfers-api
  name: Xfers Convenience Store Transfers API
  description: The Convenience Store Transfers API from Xfers — 1 operation(s) for convenience store transfers.
  humanURL: https://docs.xfers.io/Singapore
  baseURL: https://www.xfers.io/api
  tags:
  - Convenience Store Transfers
  properties:
  - type: OpenAPI
    url: openapi/xfers-convenience-store-transfers-api-openapi.yml
  - type: Documentation
    url: https://docs.xfers.io/Singapore
  - type: Documentation
    url: https://docs.xfers.io/V3/Indonesia
  - type: Documentation
    url: https://docs.xfers.io/indonesia/payment-gateway
- aid: xfers:xfers-cutting-edge-api
  name: Xfers Cutting Edge API
  description: The cutting_edge API from Xfers — 2 operation(s) for cutting_edge.
  humanURL: https://docs.xfers.io/Singapore
  baseURL: https://www.xfers.io/api
  tags: []
  tags_raw:
  - cutting_edge
  properties:
  - type: OpenAPI
    url: openapi/xfers-cutting-edge-api-openapi.yml
  - type: Documentation
    url: https://docs.xfers.io/Singapore
  - type: Documentation
    url: https://docs.xfers.io/V3/Indonesia
  - type: Documentation
    url: https://docs.xfers.io/indonesia/payment-gateway
- aid: xfers:xfers-direct-bank-transfer-payments-api
  name: Xfers Direct Bank Transfer Payments API
  description: The Direct Bank Transfer Payments API from Xfers — 1 operation(s) for direct bank transfer payments.
  humanURL: https://docs.xfers.io/Singapore
  baseURL: https://www.xfers.io/api
  tags:
  - Direct Bank Transfer Payments
  properties:
  - type: OpenAPI
    url: openapi/xfers-direct-bank-transfer-payments-api-openapi.yml
  - type: Documentation
    url: https://docs.xfers.io/Singapore
  - type: Documentation
    url: https://docs.xfers.io/V3/Indonesia
  - type: Documentation
    url: https://docs.xfers.io/indonesia/payment-gateway
- aid: xfers:xfers-disbursements-api
  name: Xfers Disbursements API
  description: API for Disbursement
  humanURL: https://docs.xfers.io/Singapore
  baseURL: https://www.xfers.io/api
  tags:
  - Disbursements
  properties:
  - type: OpenAPI
    url: openapi/xfers-disbursements-api-openapi.yml
  - type: Documentation
    url: https://docs.xfers.io/Singapore
  - type: Documentation
    url: https://docs.xfers.io/V3/Indonesia
  - type: Documentation
    url: https://docs.xfers.io/indonesia/payment-gateway
- aid: xfers:xfers-fixed-virtual-account-bank-transfers-api
  name: Xfers Fixed Virtual Account Bank Transfers API
  description: The Fixed Virtual Account Bank Transfers API from Xfers — 2 operation(s) for fixed virtual account bank transfers.
  humanURL: https://docs.xfers.io/Singapore
  baseURL: https://www.xfers.io/api
  tags:
  - Fixed Virtual Account Bank Transfers
  properties:
  - type: OpenAPI
    url: openapi/xfers-fixed-virtual-account-bank-transfers-api-openapi.yml
  - type: Documentation
    url: https://docs.xfers.io/Singapore
  - type: Documentation
    url: https://docs.xfers.io/V3/Indonesia
  - type: Documentation
    url: https://docs.xfers.io/indonesia/payment-gateway
- aid: xfers:xfers-intents-api
  name: Xfers Intents API
  description: "**For user case 1:**\r\n\r\nWhen a user is performing a top-up via  [GET /transfer_info](http://docs.xfers.io/#get-transfer-info),\
    \ they might forget to enter their contact number which is needed for our system to identify them.\r\n\r\nThe Intents\
    \ API solves this issue by requiring the user to transfer a unique amount to Xfers which will be used to identify them.\
    \ The difference between the  `unique_amount`  and the actual  `amount`  will be very small, and Xfers provides the difference\
    \ for free to the user.\r\n\r\nNote that this only acts as a backup, and the user should enter his contact number in the\
    \ comments section when doing a bank transfer whenever possible.\r\n\r\nExample: Jane wishes to transfer 5000 Indonesian\
    \ Rupiah via  `/intents`.\r\n\r\n1.  She makes a HTTP GET request to  `/user/transfer_info`  to get the correct Xfers\
    \ bank to transfer to (we have many banks!). The response tells her to transfer to Bank Central Asia (BCA).\r\n2.  She\
    \ makes a HTTP POST request to create an intent. The response tells her to make a bank transfer of 4999 to Xfers.\r\n\
    3.  Jane makes a transfer of 4999 to Xfers BCA. Within a few minutes, Xfers detects the transfer and tops up Jane’s Xfers\
    \ account with 5000. Xfers absorbs the difference for free.\r\n4.  If  `notify_url`  is given, Xfers will send a callback\
    \ to this url.\r\n\r\nNote the above scenario is only valid when disable_va is set to True\r\n\r\n**For user case 2:**\r\
    \n\r\nIntent can also be use a means to get callback notifications from Xfers when a user successfully fund their virtual\
    \ account on Xfers.\r\n\r\nExample: Jane wishes to transfer 5000 Indonesian Rupiah via  `/intents`  to her virtual Xfers\
    \ account and get a callback notification when it successful\r\n\r\n1.  She makes a HTTP POST request to create an intent\
    \ with disable_va set to false(default) and provide a  `notify_url`. The response will provide a list of virtual account\
    \ nos she can fund her account with from a list of bank that Xfers support.\r\n2.  Jane makes a transfer of 500 to the\
    \ Xfers BCA Virtual account that the intent api provide. Within a few minutes, Xfers detects the transfer and tops up\
    \ Jane’s Xfers account with 5000.\r\n3.  Since  `notify_url`  is provided, Xfers will send a callback to this url."
  humanURL: https://docs.xfers.io/Singapore
  baseURL: https://www.xfers.io/api
  tags:
  - Intents
  properties:
  - type: OpenAPI
    url: openapi/xfers-intents-api-openapi.yml
  - type: Documentation
    url: https://docs.xfers.io/Singapore
  - type: Documentation
    url: https://docs.xfers.io/V3/Indonesia
  - type: Documentation
    url: https://docs.xfers.io/indonesia/payment-gateway
- aid: xfers:xfers-loans-api
  name: Xfers Loans API
  description: Loans Management
  humanURL: https://docs.xfers.io/Singapore
  baseURL: https://www.xfers.io/api
  tags:
  - Loans
  properties:
  - type: OpenAPI
    url: openapi/xfers-loans-api-openapi.yml
  - type: Documentation
    url: https://docs.xfers.io/Singapore
  - type: Documentation
    url: https://docs.xfers.io/V3/Indonesia
  - type: Documentation
    url: https://docs.xfers.io/indonesia/payment-gateway
- aid: xfers:xfers-modify-payments-api
  name: Xfers Modify Payments API
  description: The Modify Payments API from Xfers — 1 operation(s) for modify payments.
  humanURL: https://docs.xfers.io/Singapore
  baseURL: https://www.xfers.io/api
  tags:
  - Modify Payments
  properties:
  - type: OpenAPI
    url: openapi/xfers-modify-payments-api-openapi.yml
  - type: Documentation
    url: https://docs.xfers.io/Singapore
  - type: Documentation
    url: https://docs.xfers.io/V3/Indonesia
  - type: Documentation
    url: https://docs.xfers.io/indonesia/payment-gateway
- aid: xfers:xfers-payment-queries-api
  name: Xfers Payment Queries API
  description: The Payment Queries API from Xfers — 1 operation(s) for payment queries.
  humanURL: https://docs.xfers.io/Singapore
  baseURL: https://www.xfers.io/api
  tags:
  - Payment Queries
  properties:
  - type: OpenAPI
    url: openapi/xfers-payment-queries-api-openapi.yml
  - type: Documentation
    url: https://docs.xfers.io/Singapore
  - type: Documentation
    url: https://docs.xfers.io/V3/Indonesia
  - type: Documentation
    url: https://docs.xfers.io/indonesia/payment-gateway
- aid: xfers:xfers-payment-queries-hide-first-api
  name: Xfers Payment Queries (Hide first) API
  description: The Payment Queries (Hide first) API from Xfers — 1 operation(s) for payment queries (hide first).
  humanURL: https://docs.xfers.io/Singapore
  baseURL: https://www.xfers.io/api
  tags:
  - Payment Queries (Hide first)
  properties:
  - type: OpenAPI
    url: openapi/xfers-payment-queries-hide-first-api-openapi.yml
  - type: Documentation
    url: https://docs.xfers.io/Singapore
  - type: Documentation
    url: https://docs.xfers.io/V3/Indonesia
  - type: Documentation
    url: https://docs.xfers.io/indonesia/payment-gateway
- aid: xfers:xfers-payout-api
  name: Xfers Payout API
  description: API for Payout
  humanURL: https://docs.xfers.io/Singapore
  baseURL: https://www.xfers.io/api
  tags:
  - Payout
  properties:
  - type: OpenAPI
    url: openapi/xfers-payout-api-openapi.yml
  - type: Documentation
    url: https://docs.xfers.io/Singapore
  - type: Documentation
    url: https://docs.xfers.io/V3/Indonesia
  - type: Documentation
    url: https://docs.xfers.io/indonesia/payment-gateway
- aid: xfers:xfers-registration-api
  name: Xfers Registration API
  description: Register and verify new users.
  humanURL: https://docs.xfers.io/Singapore
  baseURL: https://www.xfers.io/api
  tags:
  - Registration
  properties:
  - type: OpenAPI
    url: openapi/xfers-registration-api-openapi.yml
  - type: Documentation
    url: https://docs.xfers.io/Singapore
  - type: Documentation
    url: https://docs.xfers.io/V3/Indonesia
  - type: Documentation
    url: https://docs.xfers.io/indonesia/payment-gateway
- aid: xfers:xfers-repayments-api
  name: Xfers Repayments API
  description: API for Repayment
  humanURL: https://docs.xfers.io/Singapore
  baseURL: https://www.xfers.io/api
  tags:
  - Repayments
  properties:
  - type: OpenAPI
    url: openapi/xfers-repayments-api-openapi.yml
  - type: Documentation
    url: https://docs.xfers.io/Singapore
  - type: Documentation
    url: https://docs.xfers.io/V3/Indonesia
  - type: Documentation
    url: https://docs.xfers.io/indonesia/payment-gateway
- aid: xfers:xfers-testing-api
  name: Xfers Testing API
  description: API for testing purposes
  humanURL: https://docs.xfers.io/Singapore
  baseURL: https://www.xfers.io/api
  tags:
  - Testing
  properties:
  - type: OpenAPI
    url: openapi/xfers-testing-api-openapi.yml
  - type: Documentation
    url: https://docs.xfers.io/Singapore
  - type: Documentation
    url: https://docs.xfers.io/V3/Indonesia
  - type: Documentation
    url: https://docs.xfers.io/indonesia/payment-gateway
- aid: xfers:xfers-unique-amount-bank-transfers-api
  name: Xfers Unique Amount Bank Transfers API
  description: The Unique Amount Bank Transfers API from Xfers — 1 operation(s) for unique amount bank transfers.
  humanURL: https://docs.xfers.io/Singapore
  baseURL: https://www.xfers.io/api
  tags:
  - Unique Amount Bank Transfers
  properties:
  - type: OpenAPI
    url: openapi/xfers-unique-amount-bank-transfers-api-openapi.yml
  - type: Documentation
    url: https://docs.xfers.io/Singapore
  - type: Documentation
    url: https://docs.xfers.io/V3/Indonesia
  - type: Documentation
    url: https://docs.xfers.io/indonesia/payment-gateway
- aid: xfers:xfers-user-account-api
  name: Xfers User Account API
  description: Manage User and Accounts
  humanURL: https://docs.xfers.io/Singapore
  baseURL: https://www.xfers.io/api
  tags:
  - User Account
  properties:
  - type: OpenAPI
    url: openapi/xfers-user-account-api-openapi.yml
  - type: Documentation
    url: https://docs.xfers.io/Singapore
  - type: Documentation
    url: https://docs.xfers.io/V3/Indonesia
  - type: Documentation
    url: https://docs.xfers.io/indonesia/payment-gateway
- aid: xfers:xfers-withdraw-api
  name: Xfers Withdraw API
  description: API for Withdrawal
  humanURL: https://docs.xfers.io/Singapore
  baseURL: https://www.xfers.io/api
  tags:
  - Withdraw
  properties:
  - type: OpenAPI
    url: openapi/xfers-withdraw-api-openapi.yml
  - type: Documentation
    url: https://docs.xfers.io/Singapore
  - type: Documentation
    url: https://docs.xfers.io/V3/Indonesia
  - type: Documentation
    url: https://docs.xfers.io/indonesia/payment-gateway
- aid: xfers:xfers-esignature-api
  name: Xfers E Signature API
  description: API for e-signature
  humanURL: https://docs.xfers.io/Singapore
  baseURL: https://www.xfers.io/api
  tags:
  - E-Signature
  tags_raw:
  - ESignature
  properties:
  - type: OpenAPI
    url: openapi/xfers-esignature-api-openapi.yml
  - type: Documentation
    url: https://docs.xfers.io/Singapore
  - type: Documentation
    url: https://docs.xfers.io/V3/Indonesia
  - type: Documentation
    url: https://docs.xfers.io/indonesia/payment-gateway
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: CapabilityMap
  url: capabilities/xfers-capability-edges.yml
  name: Xfers Business Capability Map
- type: X-MCPServerCandidate
  url: mcp/xfers-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: DomainSecurity
  url: security/xfers-domain-security.yml
- type: Authentication
  url: authentication/xfers-authentication.yml
- type: Website
  url: https://xfers.com
- type: Documentation
  url: https://docs.xfers.io
- type: APIReference
  url: https://docs.xfers.io/Singapore
- type: GitHubOrganization
  url: https://github.com/Xfers
- type: StatusPage
  url: https://xfers.statuspage.io
- type: Support
  url: https://support.straitsx.com/hc/en-us/requests/new
- type: Postman
  name: Xfers Singapore Postman collection
  url: https://app.getpostman.com/run-collection/1eebf10c08b8f90bdded
- type: Postman
  name: Xfers Indonesia Postman collection
  url: https://app.getpostman.com/run-collection/453dd7b670533289a719

Xfers API — frequently asked questions

Does Xfers have an API?

Yes. APIs.io lists 20 APIs from Xfers, including Xfers Bank Account API, Xfers Charge API and Xfers Convenience Store Transfers API, and 17 more.

Is there an OpenAPI specification for the Xfers API?

Yes. APIs.io indexes 20 OpenAPI specifications for Xfers, each linked for download from this page.

How do I authenticate with the Xfers API?

Xfers uses bearer-token authentication (apiKey/http · 4 schemes). The details are profiled on APIs.io as Xfers Authentication.

Is the Xfers API ready for AI agents?

Xfers has a Kin Score of 30.3 out of 100 (thin) and an Agent Readiness score of 33.3 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/xfers"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/xfers/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/xfers/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.