Silverflow BEP Authentication API is one of 50 APIs that Silverflow publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include BEP Authentication. 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
3 operations
across 3 paths,
and defines 47 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.
3 operations3 paths47 schemas1 GET2 POST
Metadata
The identity and technical contract details declared by the specification.
Silverflow BEP Authentication 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 3
Across 3 paths, the API surfaces 3 operations — 1 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.
BEP Authentication 3
GET
/bep/{bepKey}
Get BEP
getCompleteBep1 param→ 200400401403404429500
POST
/bep
Create BEP Authentication Intent
bepbody→ 201400401403404409429500
POST
/bep/{bepKey}/authorizationResult
Finalize BEP Authentication
finalizeBep1 parambody→ 200400401403404409429500
Schemas 47
The contract defines 47 schemas that model the data the API accepts and returns. The most detailed are BepSuccessResponse (8 properties), InitiateBEPResponse (6 properties), BepInitiatedResponse (6 properties), components-schemas-InvalidInputErrorDetails (6 properties). Each schema is shown below with its type and property counts.
schemas-pan
string
Full digits of a card
AuthenticationMethod
string
ResolverByMerchant
object
Used to select a merchant acceptor by merchant key and an optional route.
2 properties1 required
AuthorizationResultAlreadySubmittedErrorDetails
object
5 properties5 required
InternalServerErrorDetails
object
5 properties5 required
schemas-expiryMonth
integer
The month the card expires. January is 1.
errorTitle
string
A short, human-readable summary of the problem type. It does not change from occurrence to occurrence of the error.
schemas-amountValue
integer
The amount in minor units. For example $12.34 should be encoded as 1234. Note that not all currencies have 2 minor units. Some have three or zero.
BepInitiatedResponse
object
BEP data which does not include sensitive information.
6 properties6 required
schemas-acceptorRoute
string
Route key used to uniquely reference an acceptor when used in combination with its card network and merchant key.
components-schemas-InvalidInputErrorDetails
object
6 properties6 required
schemas-merchantKey
string
Uniquely identifies a merchant.
schemas-EntityNotFoundErrorDetails
object
5 properties5 required
errorInstance
string
A reference that identifies the specific occurrence of the error. The instance is unique for every error.
AcceptorResolver
object
Resolver used to pick what merchant acceptor will be used to create the charge. It can accept either a combination of merchantKey and an optional route, or a m…
ResolverByAcceptorKey
object
Used to select a merchant acceptor by key.
1 property1 required
webhook
components-schemas-url
string
A valid URL
errorStatus
integer
The HTTP status code generated by the origin server for this occurrence of the problem.
components-schemas-created
schemas-acceptorKeyRef
string
Uniquely identifies a merchant acceptor.
InitiateBEPResponse
object
Response to be displayed to the payer to initiate BEP Authentication
6 properties6 required
timestamp
string
IncompatibleCardNetworkErrorDetails
object
5 properties5 required
schemas-expiryYear
integer
The year the card expires including the century.
components-schemas-currencyCode
string
The three-letter ISO code of the currency. For Bancontact only transactions with currency code EUR are allowed.
BepFailResponse
object
BEP data which does not include sensitive information.
6 properties6 required
TooManyRequestsErrorDetails
object
5 properties5 required
errorDetail
string
A human readable explanation specific to this occurrence of the problem.
UnauthenticatedBepEntityErrorDetails
object
5 properties5 required
InitiateBEPRequest
object
Request to create new a BEP authentication intent
5 properties3 required
BepSuccessResponse
object
BEP data which includes the sensitive authentication information.
8 properties8 required
AuthorizationResult
object
2 properties2 required
ReferencedEntityNotFoundErrorDetails
object
5 properties5 required
BepResponse
errorType
string
A relative URI reference, this property can be used to perform automated error handling.
schemas-AuthenticationRequiredErrorDetails
object
5 properties5 required
BSPAuthorizationResultCode
string
Bancontact Authorization action code
AuthenticationNotification
object
The notification message emitted per each initiated BEP authentication.
3 properties3 required
schemas-Amount
object
An amount encoded as an object with a value in minor units and a currency code.
2 properties2 required
schemas-AuthenticationStatus
string
The current state of the authentication.
ForbiddenErrorDetails
object
5 properties5 required
bepKey
string
Uniquely identifies a BEP authentication request flow.
completionUrl
schemas-ValidationError
object
3 properties2 required
authenticationDescription
string
An optional description to provide additional information to the cardholder in the payment approval screen of the Bancontact app.
schemas-version
integer
The version of this object
Specification
The full machine-readable OpenAPI contract behind this narrative.
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.
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 Silverflow BEP Authentication 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.
