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 Create POS Charges API

Create a POS charge.

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

Tagged areas include Create POS Charges. 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 93 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 93 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 Create POS Charges 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.

Create POS Charges 1

Create a POS charge.

POST
/pos/charges
Create Charge [EXPERIMENTAL]
createPosCharge 1 param body → 201400401403409429500

Schemas 93

The contract defines 93 schemas that model the data the API accepts and returns. The most detailed are CreateChargeResponse (18 properties), CreateChargeRequest (13 properties), schemas-AuthorizationIsoFields (8 properties), schemas-mastercardSpecificFields (7 properties). Each schema is shown below with its type and property counts.

BaseTerminal
object
2 properties 2 required
POS
components-schemas-expiryYear
integer
The year the card expires including the century
SoftPOS
schemas-ClearingStatus
string
Clearing status of the charge
CreateChargeRequest
object
Create a charge request
13 properties 5 required
isoFieldResponseCodeDescription
string
The description of the responseCode
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…
schemas-ChargeType
object
Describes the kind of POS charge the merchant wants to submit.
5 properties 4 required
PinBlockDataIso4
string
Contains encrypted PIN information, formatted as an ISO-4 block of 32 hexadecimal characters.
schemas-PinBlockIso4
object
PIN block related data in ISO-4 format.
4 properties 4 required
schemas-BaseAmountBreakdown
object
A breakdown of the transaction value. All provided amounts must exactly add up to value. Providing a breakdown is only required if any other amounts besides th…
1 property 1 required
schemas-CardInput
object
Card data
4 properties 3 required
schemas-ResponseAmount
object
The amount encoded as an object with a value in minor units and a currency code. An optional breakdown can be provided to indicate specific sub-amounts.
3 properties 2 required
softPosTerminalCapability
string
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.…
openapi_components-schemas-created
string
The date and time this object was created
isoFieldResponseCode
string
Contents of field 39
components-schemas-AcceptorResolver
object
The resolver is used to select the appropriate merchant acceptor for creating the charge. It can accept either a merchantAcceptorKey or a combination of mercha…
schemas-mastercardSpecificFields
object
Mastercard specific ISO8583 raw values
7 properties 2 required
ValidationError
object
3 properties 2 required
ReferencedEntityNotFoundErrorDetails
object
5 properties 5 required
openapi_components-schemas-amountValue
integer
An amount in minor units. For example $12.34 should be encoded as 1234.
components-schemas-intent
string
The intention of the cardholder
allowPartialApproval
boolean
Indicates whether to allow partial approvals for this charge. If set to true the charge's and the authorization action's amount field will contain the approved…
isoFieldRetrievalReferenceNumber
string
Contents of field 37
schemas-version
integer
The version of this object
components-schemas-pan
string
Full digits of a card
components-schemas-lastModified
string
The date and time this object was last modified
NonMatchingIdempotentRequestErrorDetails
object
5 properties 5 required
terminalAction
string
Indicates if the issuer requests a PIN in Single Tap mode, or switching interface.
IncompatibleCardErrorDetails
object
5 properties 5 required
errorTitle
string
A short, human-readable summary of the problem type. It does not change from occurrence to occurrence of the error.
schemas-AuthorizationIsoFields
object
Object containing the raw values from the ISO8583 response message received from the network.
8 properties 7 required
schemas-acceptorRoute
string
Route key used to uniquely reference an acceptor when used in combination with its card network and merchant key.
schemas-RequestAmountBreakdown
isoFieldSystemTraceAuditNumber
string
Contents of field 11
discoverSpecificFields
object
Discover specific ISO8583 raw values
4 properties 1 required
TerminalCapability
string
schemas-InvalidRequestErrorDetails
object
5 properties 5 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…
MissingPosAddressErrorDetails
object
5 properties 5 required
schemas-order
string
The method used to place the order.
schemas-IncompatibleCardNetworkErrorDetails
object
5 properties 5 required
chargeKey
string
Uniquely identifies a charge.
ForbiddenErrorDetails
object
5 properties 5 required
expiryMonth
integer
The month the card expires. January is 1
OutputCard
object
Card data
2 properties 1 required
amexSpecificFields
object
American Express-specific ISO8583 raw values
3 properties 1 required
schemas-clearingMode
string
The clearing method for the charge. Charges with clearingMode set to manual must be manually cleared later.
components-schemas-ResolverByAcceptorKey
object
Used to select a merchant acceptor by key.
1 property 1 required
CannotDetermineCardNetworkErrorDetails
object
5 properties 5 required
components-schemas-cardEntry
string
The method used to capture the card details.
schemas-ResponseAmountBreakdown
schemas-sequence
string
This property indicates that the cardholder has entered Online PIN, when required by the issuer for a Mastercard Single Tap transaction.
schemas-ResolverByMerchant
object
Used to select a merchant acceptor by merchant key and an optional route.
2 properties 1 required
schemas-visaSpecificFields
object
Visa specific ISO8583 raw values
6 properties 1 required
IdempotentRequestIsStillBeingProcessedErrorDetails
object
5 properties 5 required
BlockedMerchantAcceptorErrorDetails
object
5 properties 5 required
RequestAmount
object
The amount encoded as an object with a value in minor units and a currency code. An optional breakdown can be provided to indicate specific sub-amounts.
3 properties 2 required
UnauthorizedErrorDetails
object
5 properties 5 required
components-schemas-acceptorKey
string
Uniquely identifies a merchant acceptor.
components-schemas-PinBlock
object
PIN block related data.
PinBlockDataIso0Iso1
string
Contains encrypted PIN information, formatted as an ISO-0/ISO-1 block of 16 hexadecimal characters.
schemas-PinBlockKeyId
string
Encryption key in the specified zone to use.
transactionReference
string
Unique ID assigned by the merchant or payment service provider for the transaction. Used to identify the transaction.
mPOS
InternalServerErrorDetails
object
5 properties 5 required
PinBlockZoneId
string
ID of the encryption zone.
IncompatibleCardNetworkForOperation
object
5 properties 5 required
openapi_components-schemas-InvalidInputErrorDetails
object
6 properties 6 required
schemas-PinBlockIso0Iso1
object
PIN block related data in ISO-0 or ISO-1 format.
4 properties 4 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.
schemas-merchantKey
string
Uniquely identifies a merchant.
UnexpectedMessageSystem
object
5 properties 5 required
errorInstance
string
A reference that identifies the specific occurrence of the error. The instance is unique for every error.
components-schemas-AcceptorRef
object
Reference key and status of the acceptor
2 properties 2 required
localTransactionDateTime
string
Date and time of the transaction in the local timezone.
errorStatus
integer
The HTTP status code generated by the origin server for this occurrence of the problem.
schemas-processorTokenKey
string
The key to a card tokenized in the [Processor Tokenization](tag/Processor-Tokenization).
openapi_components-schemas-currencyCode-2
string
An alphabetic ISO-4217 currency code.
CreateChargeResponse
object
A POS charge
18 properties 11 required
TooManyRequestsErrorDetails
object
5 properties 5 required
errorDetail
string
A human readable explanation specific to this occurrence of the problem.
schemas-AuthorizationStatus
string
Authorization status of the charge
Terminal
object
Details about the terminal.
schemas-Status
object
The status property provides a high-level representation of the lifecycle of a charge. For a complete history, the actions should be used.
3 properties 3 required
schemas-terminalEntryMode
string
This field indicates the method used for PAN entry on the terminal to initiate the transaction.
schemas-clearAfter
string
If provided, clearing will not occur before this point in time. From August 13, 2025, clearAfter may be at most 6 months in the future from when the charge was…
errorType
string
A relative URI reference, this property can be used to perform automated error handling.
UnexpectedCurrencyErrorDetails
object
5 properties 5 required
isoFieldNetworkCode
string
Contents of field 63, subfield 1
isoFieldAuthorizationCode
string
Contents of field 38

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

silverflow-create-pos-charges-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 Management API
Silverflow Card Network Reports API
Silverflow Charge Actions API
Silverflow Charges Events API
Silverflow Charges Reports API
Where this information came from

This is an independent, third-party profile of Silverflow Create POS Charges 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.