--- swagger: "2.0" info: x-ibm-name: upitranenqapi title: UPI_Tran_Enq_API version: 2.1.0 description: This API lets a merchant know the status of a transaction, which was previously initiated by him /her. The TransactionId for which the status needs to be enquired is specified as part of TranEnqBody of the request message. contact: name: Saran K Joseph email: sarankjoseph@federalbank.co.in license: name: "" schemes: - https basePath: /upi consumes: - application/json produces: - application/json securityDefinitions: appId: type: apiKey in: header name: X-IBM-Client-Id appSecret: type: apiKey in: header name: X-IBM-Client-Secret security: - appId: [] appSecret: [] x-ibm-configuration: testable: true enforced: true phase: realized paths: /tran_enq: post: responses: 200: description: 200 OK schema: $ref: '#/definitions/Response' 400: description: error scenario schema: $ref: '#/definitions/errorResponse' 500: description: Internal Error schema: $ref: '#/definitions/errorResponse' operationId: upi_mrchnt_tran_enq parameters: - name: req required: true in: body schema: $ref: '#/definitions/Request' tags: [] definitions: Request: description: "" type: object properties: TransactionEnqReq: type: object properties: TranEnqHeader: type: object properties: SenderUserId: description: Contact Federal Bank API_Support Team for the value to be used for UAT and Production type: string SenderPassword: description: Contact Federal Bank API_Support Team for the value to be used for UAT and Production type: string SenderCode: description: Contact Federal Bank API_Support Team for the value to be used for UAT and Production type: string TranEnqBody: type: object properties: TransactionId: description: TransactionId of the original request (ReqPay), about which the status is being enquired by this API. type: string APIType: description: API Type should be “ReqAuthDetails,ReqTxnConfirmation,ReqPay”. type: string required: - SenderUserId - SenderPassword - SenderCode - TransactionId Response: description: "" type: object properties: UPITransactionEnqResp: type: object properties: TansactionId: type: string ResponseCode: type: string ResponseReason: type: string PayerVirtualId: type: string PayeeVirtualId: type: string CustomerRefNo: type: string Amount: type: number errorResponse: description: error Response Structure type: object properties: errorResponse: type: object properties: tranTimeStamp: type: string description: Server Timestamp of the transaction statuscode: type: string description: HTTP Status Code of the Transaction statusreason: type: string description: HTTP status reasonphrase of the transaction customcode: type: string description: custom reference code of the status of the transaction. customreason: type: string description: short description of the result of the transaction tranId: type: string description: Server Transaction Id description: type: string description: description of the error additionalDetails: type: object description: further details related to the transaction Response_Ack: description: "" type: object properties: UPITransactionEnqResp: type: object properties: TransactionId: type: string description: Unique and random ID to be generated by the client, for each request. In UAT, this value should always start with ‘FDR’. In Production env. the pattern will be different. ResponseCode: type: string ResponseReason: type: string x-ibm-endpoints: - endpointUrl: https://devgateway.federalbank.co.in/fedbnkdev/dev type: - production - development ...