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
Evervault

Evervault Payments API

The Payments API from Evervault — 17 operation(s) for payments.

Documentation Provider Profile APIs.io OpenAPI GitHub

Evervault Payments API is one of 4 APIs that Evervault 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 25 operations across 17 paths, and defines 33 schemas. It is described by OpenAPI 3.2.0, at version 0.0.1.

Requests are made against a single base URL, https://api.evervault.com.

25 operations 17 paths 33 schemas 4 DELETE9 GET2 PATCH10 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.0.1
Base URL
https://api.evervault.com
Authentication
HTTP Basic, HTTP Bearer, HTTP Bearer
Contact
Evervault Support Team
Resource Areas
1

Authentication & Security 3

Evervault Payments API declares 3 security schemes for authenticating requests. It accepts HTTP basic authentication (ApiKey). It accepts HTTP bearer tokens (RunToken) (TokenAuth). It accepts HTTP bearer tokens (Token) (ClientSideToken).

  • ApiKey — Authentication using an API key. The username is the App ID and the password is the Api Key.
  • TokenAuth — Authentication using a short lived run token that you can share with clients. The Authorization header must be formatted as follow: "RunToken "
  • ClientSideToken — Authentication using a short lived token that you can share with clients. The Authorization header must be formatted as follow: "Token "

Paths & Operations 25

Across 17 paths, the API surfaces 25 operations — 4 DELETE, 9 GET, 2 PATCH, 10 POST. Each is listed below with its method, path, parameters, and response codes.

Payments 25
POST
/insights/cards
Card Insights
createCardInsight body → 201
POST
/payments/bin-lookups
BIN Lookup
createBinLookup body → 201
POST
/payments/merchants
Create a Merchant
createMerchant body → 201
GET
/payments/merchants
List Merchants
listMerchants 3 params → 200
GET
/payments/merchants/{merchant_id}
Retrieve a Merchant
getMerchant 1 param → 200
PATCH
/payments/merchants/{merchant_id}
Update a Merchant
updateMerchant 1 param body → 200
DELETE
/payments/merchants/{merchant_id}
Delete a Merchant
deleteMerchant 1 param → 204
POST
/payments/acquirers
Create an Acquirer
createAcquirer body → 201
GET
/payments/acquirers
List Acquirers
listAcquirers 2 params → 200
GET
/payments/acquirers/{acquirer_id}
Retrieve an Acquirer
getAcquirer 1 param → 200
PATCH
/payments/acquirers/{acquirer_id}
Update an Acquirer
updateAcquirer 1 param body → 200
DELETE
/payments/acquirers/{acquirer_id}
Delete an Acquirer
deleteAcquirer 1 param → 204
POST
/payments/network-tokens
Create a Network Token
createNetworkToken body → 201400422500
GET
/payments/network-tokens/{network_token_id}
Retrieve a Network Token
getNetworkToken 1 param → 200
DELETE
/payments/network-tokens/{network_token_id}
Delete a Network Token
deleteNetworkToken 1 param → 204
POST
/payments/network-tokens/{network_token_id}/cryptograms
Create a Cryptogram
createNetworkTokenCryptogram 1 param → 201
POST
/payments/network-tokens/{network_token_id}/simulate
Simulate a Network Token Update
simulateNetworkTokenUpdate 1 param body → 200
GET
/payments/network-tokens/{network_token_id}/card-art
Retrieve Card Art
getCardArt 1 param → 200
POST
/payments/3ds-sessions
Create a 3DS Session
createThreeDSSession body → 201400
GET
/payments/3ds-sessions/{3ds_session_id}
Retrieve a 3DS Session
retrieveThreeDSSession 1 param → 200
GET
/payments/3ds-sessions/{3ds_session_id}/messages
Retrieve 3DS Messages
retrieveThreeDSMessages 1 param → 200
POST
/payments/cards
Register a Card
registerCard body → 200201
GET
/payments/cards/{card_id}
Retrieve a Card
getCard 1 param → 200
DELETE
/payments/cards/{card_id}
Delete a Card
deleteCard 1 param → 204
POST
/payments/cards/{card_id}/simulate
Simulate a Card Update
simulateCardUpdate 1 param body → 200

Schemas 33

The contract defines 33 schemas that model the data the API accepts and returns. The most detailed are ThreeDSSession (22 properties), Card (16 properties), BinLookup (12 properties), NetworkToken (11 properties). Each schema is shown below with its type and property counts.

CauNanUpdate
object
New account number
3 properties 1 required
CardInsight
object
10 properties 4 required
PaymentOneOff
object
A payment that is made in a single transaction.
3 properties 3 required
AcquirerConfiguration
object
5 properties 4 required
ThreeDSAccessControlServer
object
Details about the Access Control Server involved in the 3DS transaction.
3 properties
PaymentInstallment
object
A repeating payment for paying a total amount in multiple installments.
6 properties 5 required
Acquirer
object
The acquirer of the payment.
3 properties 3 required
BinLookup
object
12 properties
NetworkTokenCryptogram
object
3 properties 3 required
ThreeDSSession
object
The 3D Secure API can be used in combination with our [Client-Side SDK's](/sdks/javascriptuithreedsecure) to authenticate cardholders using 3D Secure. This API…
22 properties 7 required
NetworkToken
object
11 properties 9 required
Merchant
object
10 properties 4 required
Error
object
5 properties
CardInsightAddress
object
4 properties
CardInsightCapabilities
object
7 properties
Address
object
6 properties 4 required
ThreeDSChallenge
object
Details about the 3DS challenge.
2 properties 1 required
CauAclUpdate
object
Account closure
1 property 1 required
CardThreeDSMetadata
object
Metadata about 3DS capabilities, including supported versions and ACS (Access Control Server) indicators.
2 properties
CardInsightCardholder
object
4 properties
CardFastFunds
object
Specifies the availability of instant payment capabilities for card transactions, indicating whether funds can be transferred immediately both within the same…
2 properties
ThreeDSDirectoryServer
object
Details about the Directory Server involved in the 3DS transaction.
3 properties
MerchantApplePay
object
1 property
MerchantNetworkTokenStatus
object
1 property
CardArt
object
4 properties 4 required
CardExpiry
object
2 properties 2 required
CauNedUpdate
object
New expiry date
2 properties 1 required
ThreeDSInitiator
object
Details about the transaction initiation process.
CardFunding
string
The card funding type specifies the method by which transactions are financed.
CardSegment
string
The card segment indicates the primary market or usage category of the card.
PaymentRecurring
object
A repeating payment with a regular interval.
5 properties 5 required
Card
object
16 properties 4 required
CardBrand
string
The card brand associated with the payment card.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

evervault-payments-api-openapi.yml Raw ↑

Other APIs Evervault publishes across the network.

Evervault Core API
AE Profile APIs.io
Evervault Webhooks API
AE Profile APIs.io
Evervault Evervault API
AE Profile APIs.io
#Payments
← Back to E APIs
API Details
ID
evervault:evervault-payments-api
Base URL
https://api.evervault.com
Docs
https://docs.evervault.com/api
Provider
Evervault
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=evervault-payments-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/evervault-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 Evervault 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.