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

Silverflow Card Management API

ATM card management actions: PIN change, PIN unblock, balance inquiry andPIN change reversal.

Silverflow Card Management API is one of 50 APIs that Silverflow publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Card Management. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.

This API exposes 1 operation across 1 path, and defines 43 schemas. It is described by OpenAPI 3.2.0, at version 1.417.0.

Requests are made against 3 base URLs: https://eu-west-1.api.silverflow.com/v1, https://us-east-2.api.silverflow.com/v1, https://eu-west-1.api-sbx.silverflow.com/v1.

1 operations 1 paths 43 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.417.0
Base URL
https://eu-west-1.api.silverflow.com/v1
Authentication
HTTP Basic, HTTP Bearer, API Key
License
Commercial
Resource Areas
1

Authentication & Security 3

Silverflow Card Management API declares 3 security schemes for authenticating requests. It accepts HTTP basic authentication (ApiKey). It accepts HTTP bearer tokens (JWT) (BearerToken). An API key is passed in the header as - (MutualTLS). By default, every request must be authenticated.

  • ApiKey — The primary method of authenticating to the Silverflow API is through API keys. API keys can be created by calling the [createApiKey](operation/createApiKey) e…
  • BearerToken — Bearer tokens are temporary security credentials that can be used to authorize 'third parties' (bearers) access to the Silverflow API on behalf of the agent. T…
  • MutualTLS — The client must set up mTLS connection with a valid X.509 client certificate signed by a customer-provided CA (certificate authority) that is registered to a s…

Paths & Operations 1

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

Card Management 1

ATM card management actions: PIN change, PIN unblock, balance inquiry and PIN change reversal.

POST
/cardManagement/actions/pinUnblock
Unblock PIN [EXPERIMENTAL]
CreatePinUnblock body → 201400401403409429500

Schemas 43

The contract defines 43 schemas that model the data the API accepts and returns. The most detailed are PinUnblockResponse (12 properties), PinUnblockRequest (10 properties), AuthorizationIsoFields (7 properties), InvalidInputError (6 properties). Each schema is shown below with its type and property counts.

NewEmvData
string
This field contains integrated circuit card (ICC) related binary data that is transmitted from the card issuer to the ICC. This field is formatted as 510 hexad…
InvalidInputError
object
6 properties 6 required
MerchantAcceptorRef
object
2 properties 2 required
UnauthorizedError
object
5 properties 5 required
BlockedMerchantAcceptorError
object
5 properties 5 required
ActionResult
string
The result of the authorization.
IncompatibleNetworkForOperationError
object
5 properties 5 required
schemas-TerminalCapability
string
ATM terminal capabilities subset
NetworkSpecificFields
MerchantAcceptorKeyResolver
object
Used to select a merchant acceptor by key.
1 property 1 required
CardSequenceNumber
string
Distinguishes among separate cards having the same PAN. This is required if EMV tag 5F34 is present/personalized on the card chip.
errorInstance
string
A reference that identifies the specific occurrence of the error. The instance is unique for every error.
ForbiddenError
object
5 properties 5 required
components-schemas-Card
object
Card details for ATM transactions.
3 properties 3 required
Track2Data
string
The information encoded on track 2 of the card magnetic stripe as defined in the ISO 7813 specification, including data element separator but excluding the beg…
MerchantAcceptorKey
string
Uniquely identifies a merchant acceptor.
IncompatibleMccError
object
5 properties 5 required
schemas-Terminal
object
Details about the ATM terminal.
2 properties 2 required
IdempotentRequestMismatchError
object
5 properties 5 required
MerchantAcceptorResolver
The resolver is used to select the appropriate merchant acceptor for the action. It can accept either a merchantAcceptorKey or a combination of merchantKey and…
TooManyRequestsError
object
5 properties 5 required
ReferencedEntityNotFoundError
object
5 properties 5 required
errorDetail
string
A human readable explanation specific to this occurrence of the problem.
MerchantKey
string
Uniquely identifies a merchant.
PinUnblockResponse
object
12 properties 9 required
LocalTransactionDateTime
string
Date and time of the transaction in the local timezone.
PinUnblockRequest
object
10 properties 6 required
MerchantKeyResolver
object
Used to select a merchant acceptor by merchant key and an optional route.
2 properties 1 required
CannotDetermineCardNetworkError
object
5 properties 5 required
schemas-PinBlock
object
PIN block related data in ISO-4 format.
4 properties 4 required
IdempotentRequestIsStillBeingProcessedError
object
5 properties 5 required
VisaNetworkFields
object
Visa specific ISO8583 raw values
1 property 1 required
MastercardNetworkFields
object
Mastercard specific ISO8583 raw values
2 properties 2 required
ReferencedAcceptorNotFoundByRouteError
object
5 properties 5 required
InvalidRequestError
object
5 properties 5 required
MaskedCard
object
Card data for ATM transactions. ATM transactions do not support processor tokenization.
1 property 1 required
AuthorizationIsoFields
object
The values from the ISO8583 response message received from the network.
7 properties 6 required
components-schemas-ValidationError
object
3 properties 2 required
InternalServerError
object
5 properties 5 required
TransactionReference
string
Unique ID assigned by the merchant or payment service provider for the transaction. Used to identify the transaction.
ActionKey
string
Uniquely identifies a card-management action.
EmvData
string
This field contains integrated circuit card (ICC) related binary data that is transmitted from the ICC to the card issuer and from the card issuer to the ICC.…
TerminalEntryMode
string
The method used for PAN entry on the ATM terminal.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

silverflow-card-management-api-openapi.yml Raw ↑

Other APIs Silverflow publishes across the network.

Silverflow 3DS Authentication API
Silverflow Agents API
Silverflow AMMF Submission Events API
Silverflow API Keys API
Silverflow BEP Authentication API
Silverflow Bins API
Silverflow Card Info API
Silverflow Card Network Reports API
Silverflow Charge Actions API
Silverflow Charges Events API
Silverflow Charges Reports API
Silverflow Clearing Events API
Where this information came from

This is an independent, third-party profile of Silverflow Card Management 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.