Update gateway score
OpenAPI: Score Feedback
Update Gateway Score
Feed a transaction outcome back into the success-rate model. Call this after every transaction so the engine has accurate SR data for future routing decisions.
POST
Update gateway score
Update Gateway Score
Use case
Records the observed transaction outcome for a previously selected gateway so auth-rate analytics can learn from real payment results.Authentication
Protected. Send eitherAuthorization: Bearer <jwt_token> or x-api-key: <api_key>. In sandbox, also send x-feature: decision-engine.
For local development, start with:
Request
- Method and path:
POST /update-gateway-score - Parameters: none.
- Body: JSON body should include merchant/payment identity, selected gateway, status, and latency/outcome details expected by the score updater.
Example
Update gateway score
Response
Notes
- Do not call this after
NTW_BASED_ROUTINGjust to record the selected debit network; debit audit comes from/decide-gatewayanalytics. - Call it after payment authorization completes, not before.
Related
Authorizations
JWT token obtained from /auth/login
Body
application/json
Example:
"test_merchant"
Example:
"stripe"
Example:
"pay_001"
Available options:
CHARGED, AUTHENTICATION_FAILED, AUTHORIZATION_FAILED, JUSPAY_DECLINED, FAILURE Example:
"CHARGED"
Example:
"stripe_ref_001"