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

Enfuce Authorisation Request API

The Authorisation Request API API from Enfuce — 1 operation(s) for authorisation request api.

Enfuce Authorisation Request API is one of 7 APIs that Enfuce publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Authorisation Request API. The published artifact set on APIs.io includes an OpenAPI specification.

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

Requests are made against 2 base URLs: https://api.{{tenant}}.ext-uat1-sandbox.mycore.enfuce.com/processor, https://api.{{tenant}}.eu.live.prod.mycore.enfuce.com/processor.

1 operations 1 paths 22 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.{{tenant}}.eu.live.prod.mycore.enfuce.com/issuer
Resource Areas
1

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.

Authorisation Request API 1
POST
/auth
Authorisation Request API
authPost body → 200

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are transaction (16 properties), merchant (13 properties), card (7 properties), authorizationMetadata (4 properties). Each schema is shown below with its type and property counts.

currency
string
A valid ISO 4217 currency code
authResponseBody
object
3 properties 1 required
authRequestBody
messageFunctionAuthorization
string
Identifies the message function of the authorisation request.
transaction
object
16 properties
account
object
1 property 1 required
authResponseCode
string
Indicates whether the authorisation request is approved or declined. Possible enums: APPROVED - Approved PARTIALLYAPPROVED - Approved for partial amount DONOTH…
cardholderVerificationMethod
string
The method used for verifying the cardholder: - PINVERIFIEDBYCARD: The card's PIN is verified. - PINVERIFIEDBYISSUER: The card's PIN is verified by issuer. - W…
id
string
Unique system generated ID assigned to each event in the payment processing workflow. For example, an ID assigned to the initial authorisation event.
messageCategoryAuthorization
string
Message category sent in the authorisation control webhook. Possible enums: - INITIALAUTHORIZATION: Initial authorisation of the card payment. - INCREMENTALAUT…
token
object
Information about the token associated with the card.
2 properties
country
string
A valid ISO-3166-1 alpha-3 country code.
transactionFee
object
2 properties
authorizationMetadata
object
4 properties
merchant
object
13 properties
approvedTransaction
expiration
object
2 properties 2 required
card
object
Information about the card used for the payment.
7 properties
transactionType
string
The transaction Type
money
object
Amount including currency.
2 properties 2 required
transactionId
string
Enfuce generated unique ID assigned to each card transaction. Transaction events for the same card payment includes the same transactionId. For example, author…
cardEntryMode
string
Describes how the card credentials were captured.

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

enfuce-authorisation-request-api-api-openapi.yml Raw ↑

Other APIs Enfuce publishes across the network.

Enfuce Create Card API
Enfuce Create PIN Control access token API
Enfuce Get card API
Enfuce Get Card Payment Info API
Enfuce Get plastic manufacturing history API
Enfuce Update card API
Where this information came from

This is an independent, third-party profile of Enfuce Authorisation Request 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.