Authorization Callback

Description

Miden sends an HTTP POST request to your configured Authorization URL whenever a supported card transaction event requires processing under the Customer-Managed Authorization model.

The callback provides transaction, merchant, authorization, settlement, charge, and risk information that your system can use when evaluating the transaction.

Your system evaluates the request using your own authorization rules and returns an approval or decline decision within the agreed response time.

Where available, Miden also includes a riskAssessment object containing an advisory assessment of transaction risk based on the signals available for the transaction.

Usage

Implement this endpoint in your system and configure its publicly accessible URL under:

Miden Portal → Settings → Developer → Card Transaction Authorizations

Your endpoint must:

• Accept HTTP POST requests.
• Accept JSON.
• Validate the request using the required authentication/signature mechanism.
• Evaluate the transaction and return a supported authorization decision.
• Return HTTP 200 OK for a valid authorization response.
• Respond within the agreed response time.

Miden applies the decision returned by your system. Where no valid response is received within the agreed response time, Miden applies your configured Default Authorization Decision.

Charge Types

The chargeType field identifies the type of charge contained in the charge field.

Contactless Charge

When a charge applies to a contactless transaction, Miden provides the charge during the authorization request.

Example:

{
"requestType": "Authorization",
"charge": 1.50,
"chargeType": "ContactlessCharge",
"isContactlessPayment": true
}

isContactlessPayment indicates that the transaction was performed using contactless payment, while chargeType identifies the applicable charge.

Cross-Border Charge

Cross-border charges are provided during the settlement stage rather than during the initial authorization.

Example:

{
"requestType": "Settlement",
"charge": 2.75,
"chargeType": "CrossBorderCharge"
}

You should therefore not expect a cross-border charge to necessarily be available during the initial authorization request.

Amount and Currency Interpretation

For Customer-Managed Authorization, the transaction amounts should be interpreted as follows:

For example:

{
"transactionAmount": 3.75,
"authorizationAmount": 19000,
"transactionCurrencyCode": "BRL"
}

This represents:

• transactionAmount: USD 3.75
• authorizationAmount: BRL 19,000
• transactionCurrencyCode: BRL

Endpoint

This endpoint is hosted by you.
Example:

POST https://api.yourcompany.com/cards/authorizations

Risk Assessment

Miden may include a riskAssessment object in card authorization and transaction events to help you evaluate the risk profile of a transaction before making an authorization or downstream processing decision.

The assessment combines available transaction signals such as:

• Card verification
• 3DS authentication
• AVS
• Card-present or card-not-present context
• Tokenization
• Stored credentials
• Recurring-payment indicators
• Transaction value
• Other available authorization attributes

The assessment is advisory. You remain responsible for the final authorization decision and may combine the assessment with your own balance, fraud, velocity, card-control, compliance, and transaction-monitoring rules.