---
title: "Mandate Presentation Callback"
method: POST
path: "/upi_presentation_status1"
---

# Mandate Presentation Callback

`POST /upi_presentation_status1`

This callback is triggered by Decentro to the platform when a debit request is executed

## Headers

- `your_custom_header_key_1` string
- `your_custom_header_key_2` string

## Request body

- object
  - `presentation_status` string — Debit status of the presentation
  - `presentation_status_description` string — Description of the debit status of the presentation. Failure reason will be found here
  - `presentation_sequence_id` string — The presentation sequence ID of the presentation cycle
  - `remaining_representation_attempts` integer — The number of retry attempts pending for a failed presentation attempt in a given presentation cycle. Max retries: 9
  - `presentation_auth_timestamp` string — The user authentication timestamp of presentation collect request in case amount is more than the threshold.
  - `decentro_txn_id` string — The decentro Txn ID of the presentation
  - `callback_attempt` integer — The number of times the callback is attempted
  - `callback_txn_id` string — Callback ID provided by Decentro
  - `consumer_urn` string, required — The URN of the entity against which the mandate was registered.
  - `callback_timestamp` string — The timestamp of the callback
  - `original_callback_txn_id` string — Original Callback ID. Shared in case of retries only
  - `reference_id` string, required — The reference ID passed by the platform at the time of Presentation API. For instant presentations, Reference ID will be mapped to Create Mandate APIs reference_id
  - `bank_reference_number` string — Reference number for the presentation
  - `npci_txn_id` string — The NPCI txn ID of the presentation.
  - `payer_vpa` string — UPI handle against which the funds are deducted.
  - `decentro_mandate_id` string — Unique decentro mandate ID assigned for each mandate.
  - `amount` number, double — Mandate registration amount
  - `amount_rule` string — Amount rule as defined at the time of registration
  - `payer_name` string — Payer name against whom the mandate is registered
  - `payee_name` string — The Name of the of the sub-merchant onboarded account
  - `next_debit_date` string, date — Next debit date. Applicable if frequency is not ASPRESENTED
  - `mandate_name` string — Name of the mandate holder as passed during registration
  - `frequency` string — Mandate registration frequency
  - `start_date` string, date — Mandate start date
  - `end_date` string, date — Mandate end date
  - `presentation_summary` object — Summary of presentation counts
    - `total` integer — total number of presentation for the mandate
    - `success` integer — Total successful presentation for the mandate
    - `failed` integer — Total failed presentation for the mandate
    - `skipped` integer — Total skipped presentation for the mandate
    - `remaining` integer — Total remaining presentation for the mandate
  - `rule_type` string — The rule type of the mandate as passed during registration
  - `block_fund` boolean — Blocking the funds during the debit presentation. Only true to selceted merchants.
  - `is_revocable` string — The flag denotes whether the end user will be able to revoke a mandate.
  - `last_action` string — The last action performed on the mandate. Example: CREATE, UPDATE, PAUSE
  - `last_action_timestamp` string — The timestamp when the last action of performed on the mandate.
  - `error_key` string — Presentation failure reason bucketing.
  - `error_key_description` string — NPCI error code & reason for failure

## Response `200`

200

- object
  - `response_code` string

---

[API](https://skmtc.dev/decentro/apis/decentro-staging.md) · [All operations](https://skmtc.dev/decentro/apis/decentro-staging/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/decentro/decentro-staging/revisions/f1a86ce4638c/schema)