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
Lorum

Lorum Payments API

The Payments API from Lorum — 2 operation(s) for payments.

Documentation Provider Profile APIs.io OpenAPI GitHub

Lorum Payments API is one of 10 APIs that Lorum publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payments. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 2 operations across 2 paths, and defines 17 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against 2 base URLs: https://api.fuse.me, https://api-sandbox.fuse.me.

2 operations 2 paths 17 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.fuse.me
Authentication
HTTP Bearer
Contact
Lorum
License
Proprietary license
Resource Areas
1

Authentication & Security 1

Lorum Payments API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (OAuth2). By default, every request must be authenticated.

Paths & Operations 2

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

Payments 2
POST
/v1/accounts/{account_id}/payments
Create outbound payment for a customer
create_customer_payment 2 params body → 202400404409422
GET
/v1/accounts/{account_id}/payments/estimate-fee/{amount}
Estimate the fee for an outbound payment
customer_payment_fee_estimate 2 params → 200400404

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are PaymentDetails (10 properties), EstimateFeeResponse (6 properties), CreateCustomerPaymentRequest (5 properties), Address (5 properties). Each schema is shown below with its type and property counts.

EstimateFeeResponse
object
6 properties 6 required
AccountDetailsIdentifier
PaymentDetails
object
Account details of the payment beneficiary.
10 properties 4 required
Currency
string
CreateCustomerPaymentRequest
object
Parameters required to create a payment.
5 properties 4 required
Address
object
5 properties 2 required
uae_id
object
1 property 1 required
ScanDetails
object
2 properties 2 required
WireBankDetails
object
2 properties 2 required
CreatePaymentResponse
object
1 property 1 required
BeneficiaryBank
object
Bank details of payment beneficiary bank.
3 properties
BicCode
string
BIC Code to identify a bank.
Identification
The identification field is not required. When provided, then all UAEID fields or PASSPORT fields are required.
passport
object
2 properties 2 required
CounterpartType
string
IntermediaryBank
object
2 properties 1 required
PurposeCode
string
Enum representing different payment purposes.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lorum-payments-api-openapi.yml Raw ↑

Other APIs Lorum publishes across the network.

Lorum Accounts API
AE Profile APIs.io
Lorum Customers API
AE Profile APIs.io
Lorum Customers V2 API
AE Profile APIs.io
Lorum Documents API
AE Profile APIs.io
Lorum Exchange API
AE Profile APIs.io
Lorum Internal Transfers API
AE Profile APIs.io
Lorum Oauth API
AE Profile APIs.io
Lorum Simulation API
AE Profile APIs.io
Lorum Transactions API
AE Profile APIs.io
#Payments
← Back to L APIs
API Details
ID
lorum:lorum-payments-api
Base URL
https://api.fuse.me
Docs
https://docs.lorum.com/docs/getting-started
Provider
Lorum
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=lorum-payments-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/lorum-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 Lorum 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.