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
Weavr

Weavr Card Payments API

Retrieve card payment activity, including authorisations, settlements, and related events.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

This API exposes 3 operations across 3 paths, and defines 16 schemas. It is described by OpenAPI 3.2.0, at version v3.

Requests are made against a single base URL, https://sandbox.weavr.io/multi.

3 operations 3 paths 16 schemas 3 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v3
Base URL
https://api.weavr.io/multi
Authentication
API Key, HTTP Bearer, API Key
Contact
Weavr
Resource Areas
1

Authentication & Security 3

Weavr Card Payments API declares 3 security schemes for authenticating requests. An API key is passed in the header as api-key (api-key). It accepts HTTP bearer tokens (JWT) (auth_token). An API key is passed in the header as webhooks-key (webhooks_key).

  • api-key — An API key defined in your User API Client (or Delegate API Client - this feature is available only to customers enabled with delegation functionality). API Cl…
  • auth_token — The authentication token representing the user. This will be included in the login response object.
  • webhooks_key — The Webhooks key can be found in the API Credentials tab in your Portal Page.

Paths & Operations 3

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

Card Payments 3

Retrieve card payment activity, including authorisations, settlements, and related events.

GET
/card_payments
Get all card payments
cardPaymentsGet 16 params → 200400401500default
GET
/card_payments/{id}
Get a single card payment
cardPaymentGet 1 param → 200401404500default
GET
/card_payment_events
Get all card payment events
cardPaymentEventsGet 11 params → 200400401500default

Schemas 16

The contract defines 16 schemas that model the data the API accepts and returns. The most detailed are Merchant (16 properties), CardPayment (11 properties), Card (10 properties), CardPaymentList (3 properties). Each schema is shown below with its type and property counts.

CardPayment
object
One card transaction's full lifecycle — authorisation, settlement, refunds — as a single resource that the platform keeps up to date as scheme events arrive. D…
11 properties 8 required
CardPaymentType
string
High-level type of card payment, derived from the first event. - PURCHASE — standard purchase at a merchant. - REFUND — refund from a merchant to the cardholde…
CurrencyAmount
object
The object representing a monetary amount in a particular currency.
2 properties 2 required
CardPaymentSubtype
string
Scheme-network subtype that further classifies an event. Reversal-vs-original lives on the separate reversal field on each event.
Merchant
object
Information about a merchant — used wherever a merchant appears in card-payment flows, statement entries, and transaction activity.
16 properties 2 required
SyntaxError
object
Is returned as part of an HTTP error response whenever a syntax error is detected. A list of the fields together with their syntax error will be provided.
1 property
CardPaymentList
object
Paginated list of CardPayments.
3 properties
Error
object
2 properties
CardPaymentEvent
object
An event in a card payment's lifecycle, lean — used nested inside CardPayment.events[]. The parent card payment provides cardPaymentId, card, and merchant, so…
1 property 1 required
CardPaymentEventDetail
object
Standalone card payment event — same four variants as CardPaymentEvent, but each row also carries the parent CardPayment context (cardPaymentId, card, merchant…
1 property 1 required
CardPaymentEventList
object
Paginated list of CardPaymentEventDetail.
3 properties
ProfileId
string
The profile Id which a specific identity, instrument or transaction type is linked to. Profiles contain configuration and determine behavioral aspects of the n…
CardPaymentEventType
string
Type of event recorded against a CardPayment. The reversal flag on each event distinguishes a reversal from the original action.
Currency
string
The currency expressed in ISO-4217 code. Example: GBP, EUR, USD.
Card
object
Information about a managed card — used wherever a card appears (the card on a card payment, or the access instrument that initiated a transaction).
10 properties 2 required
CardPaymentStatus
string
Lifecycle status of a CardPayment. - SETTLEMENTINPROGRESS — authorised, not yet (or not fully) settled. The hold is still on the card. - SETTLED — fully settle…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

weavr-card-payments-api-openapi.yml Raw ↑

Other APIs Weavr publishes across the network.

Weavr Access Token API
AE Profile APIs.io
Weavr Access Tokens API
AE Profile APIs.io
Weavr Accounts API
AE Profile APIs.io
Weavr Additional Factors API
AE Profile APIs.io
Weavr Authentication Factors API
AE Profile APIs.io
Weavr Authorised Signatories API
AE Profile APIs.io
Weavr Authorised Users API
AE Profile APIs.io
Weavr Buyer Authorised Users API
AE Profile APIs.io
Weavr Buyers API
AE Profile APIs.io
Weavr Cards API
AE Profile APIs.io
Weavr Confirmation Challenges API
AE Profile APIs.io
Weavr Consumers API
AE Profile APIs.io
#Card Payments
← Back to W APIs
API Details
ID
weavr:weavr-card-payments-api
Base URL
https://api.weavr.io/multi
Docs
https://api.weavr.io/products/multi/openapi
Provider
Weavr
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=weavr-card-payments-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/weavr-card-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 Weavr Card 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.