Decentro Deposit Simulation API

The Deposit Simulation API from Decentro — 1 operation(s) for deposit simulation.

Operations 1

POST /deposit_simulation/ecollect Simulate E-collect Transaction (Staging) - PA platform #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/decentro:decentro-deposit-simulation-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

decentro-deposit-simulation-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Decfin Staging Deposit Simulation API
  version: '1.0'
servers:
- url: https://staging.api.decentro.tech
security:
- {}
tags:
- name: Deposit Simulation
paths:
  /deposit_simulation/ecollect:
    post:
      summary: Simulate E-collect Transaction (Staging) - PA platform
      description: This API can be used in our Staging environment to simulate an incoming E-Collect Transaction for a specific Virtual Account
      operationId: simulate-e-collect-transaction-staging
      requestBody:
        content:
          application/json:
            schema:
              type: object
              required:
              - account_number
              - ifsc
              - name
              - amount
              - transfer_type
              - remarks
              - bank_reference_number
              properties:
                beneficiary_details:
                  type: string
                  description: This block will contain the details of the beneficiary or the destination Virtual Account
                account_number:
                  type: string
                  description: The Account number of the remitter. This is the account from which the funds are being loaded.
                ifsc:
                  type: string
                  description: The IFSC code mapped to the remitter account. This is the account from which the funds are being loaded.
                remitter_details:
                  type: string
                  description: This block will contain the details of the remitter, aka, the sender.
                name:
                  type: string
                  description: The name of remitter, aka, the sender.
                transfer_details:
                  type: string
                  description: This block will contain the details of the the fund transfer
                amount:
                  type: string
                  description: The transfer amount. Up to 2 decimal places are supported.
                transfer_type:
                  type: string
                  description: 'The channel through which the funds are transferred. Possible values are: IMPS, NEFT, RTGS'
                remarks:
                  type: string
                  description: The purpose message or reason for the fund transfer.
                bank_reference_number:
                  type: string
                  description: The bank reference number associated with the fund transfer. This value will be propagated in our callbacks for ease of reconciliation.
            examples:
              Sample Request:
                value:
                  beneficiary_details:
                    account_number: YBLTRU6340378299288
                    ifsc: YES0000106
                  remitter_details:
                    account_number: '026431500007721'
                    ifsc: YESB0CMSNOC
                    name: Mocked Remitter
                  transfer_details:
                    amount: 100
                    transfer_type: IMPS
                    remarks: Test Credit
                    bank_reference_number: '986700002'
      responses:
        '200':
          description: '200'
          content:
            application/json:
              examples:
                API Response:
                  value: "{\n    \"message\": \"Deposit request accepted.\",\n    \"response_key\": \"success_deposit_request_accepted\"\n}"
              schema:
                type: object
                properties:
                  message:
                    type: string
                    example: Deposit request accepted.
                  response_key:
                    type: string
                    example: success_deposit_request_accepted
      deprecated: false
      tags:
      - Deposit Simulation
x-readme:
  headers: []
  explorer-enabled: true
  proxy-enabled: true
x-readme-fauxas: true
x-provenance:
  method: harvested
  publisher: Decentro
  source: https://docs.decentro.tech/openapi/65e59db4d5a4dc005d972404
  note: split by refine-openapis from the provider's own published document, verified by fetch (openapi/_original/*.fetch.json);
    stamped by stamp-openapi-provenance.py (roadmap#793)