How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Fave

Fave Payments API

Create charges via QR code or merchant scan.

Documentation Provider Profile APIs.io OpenAPI GitHub

Fave Payments API is one of 2 APIs that Fave publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Payments. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an AsyncAPI specification.

This API exposes 2 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.1.0, at version v1.

Requests are made against 2 base URLs: https://omni.myfave.com, https://omni.dino.fave.ninja.

2 operations 2 paths 5 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v1
Base URL
https://omni.myfave.com
Authentication
API Key
Contact
Fave Partner Support
Resource Areas
1

Authentication & Security 1

Fave Payments API declares 1 security scheme for authenticating requests. An API key is passed in the query as sign (hmacSignature). By default, every request must be authenticated.

  • hmacSignature — HMAC-SHA256 signature computed over the URL-encoded request fields in submission order (excluding sign and countrycode, and excluding outletid on list, id on a…

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 POST. Each is listed below with its method, path, parameters, and response codes.

Payments 2

Create charges via QR code or merchant scan.

POST
/api/fpo/v1/{country_code}/qr_codes
Create a single-use QR code or payment URL
createQrCode 1 param body → 200400401404422500
POST
/api/fpo/v1/{country_code}/merchant_scan
Process a customer-presented QR / barcode (merchant scan)
merchantScan 1 param body → 200400401404422500

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Transaction (39 properties), CreateQrCodeRequest (12 properties), MerchantScanRequest (8 properties), CreateQrCodeResponse (3 properties). Each schema is shown below with its type and property counts.

MerchantScanRequest
object
8 properties 6 required
Transaction
object
39 properties
CreateQrCodeRequest
object
12 properties 5 required
CreateQrCodeResponse
object
3 properties
Error
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

fave-payments-api-openapi.yml Raw ↑

Other APIs Fave publishes across the network.

Fave Transactions API
AE Profile APIs.io
#Payments
← Back to F APIs
API Details
ID
fave:fave-payments-api
Base URL
https://omni.myfave.com
Docs
https://developers.myfave.com/fpo-guide.html
Provider
Fave
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=fave-payments-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/fave-payments-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of Fave Payments API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.