Transaction Status API
Checksum required: Yes
Use Case:
• To
re-confirm the status of exchange before conveying the item or administration
to the client, vendor needs to coordinate the Order ID and exchange sum
returned in the reaction of this API against that sent in exchange demand. In
the event of befuddle, item or administration ought not be satisfied. Furthermore,
the terminal status of exchange gave ought to be treated as the last status of
exchange.
• To
get status of an installment exchange where constant reaction was not given
(because of framework disappointments, API break and so on.).
• To
get terminal status of exchange when the status was conveyed as pending
accordingly of procedure exchange.
ATTRIBUTE
|
DESCRIPTION
|
MANDATORY
|
MID
String(20)
|
This
is a remarkable identifier given to each dealer by Paytm. MID is a piece of
your record certifications and is diverse on arranging and creation
condition. Your organizing MID is accessible here and creation MID will be
accessible once your enactment is complete
|
Yes
|
ORDERID
|
String(50) Order ID is vendor's exceptional
reference ID for an exchange went in the exchange payload. This is Order ID
for which the exchange status should be fetched
|
Yes
|
CHECKSUMHASH
|
String(108) Signature to abstain from altering.
Produced utilizing server side checksum utility accessible here.
|
Yes
|
TXNTYPE
String(10)
|
The
kind of exchange whose status should be checked by dealer conceivable worth
PREAUTH/RELEASE/CAPTURE/WITHDRAW.
|
No
|
Response Attribute
ATTRIBUTE
|
DESCRIPTION
|
MID
String(20)
|
This
is an extraordinary identifier given to each dealer by Paytm
|
TXNID
String(64)
|
This
is an exceptional Paytm exchange ID comparing to Ordered ID for which status
is being checked.
|
ORDERID
String(50)
|
Order
ID is vendor's one of a kind reference ID for an exchange sent in demand.
|
BANKTXNID
String(50)
|
The
exchange ID sent by the bank. In the event of Paytm restrictive instruments
as well, there is interesting reference number produced by Paytm's framework.
On the off chance that the exchange doesn't arrive at the bank, this will be
NULL or void string. Essential purpose behind this is client dropping out of
the installment stream before the exchange compasses to bank to servers
|
TXNAMOUNT
String(10)
|
Order
estimation of the exchange in INR. Vendor ought to approve this sum against
that send in exchange demand payload. On the off chance that the sum doesn't
coordinate, trader ought not offer the types of assistance to client. This is
expected to maintain a strategic distance from solicitation and reaction
altering conceivable at the hour of exchange.
|
STATUS
String(20)
|
This
contains the exchange status and has just three qualities: TXN_SUCCESS,
TXN_FAILURE and PENDING.
|
RESPCODE
String(10)
|
Codes
allude to a specific explanation of installment disappointment. Rundown right
now.
|
RESPMSG
String(500)
|
Description
message joined with each respcode. Rundown right now.
|
TXNDATE
|
DateTime Date and time of exchange in the
configuration "yyyy-MM-dd HH:mm:ss.S"
Eg-"2015-11-02
11:40:46.0"
|
GATEWAYNAME
String(15)
|
Gateway
utilized by Paytm to process the exchanges. For Credit,Debit Cards and UPI -
Gateway used to process the exchange.
For
instance, if HDFC door has been utilized to process SBI charge card
exchanges, the worth will be HDFC.
For
Net banking and wallet, worth will be Issuing Bank name and Wallet
separately.
|
BANKNAME
String(500)
|
Name
of giving bank of the installment instrument utilized by client. For Credit
Cards, Debit Cards, Netbanking - Name of the giving bank.
Model
in the event that client utilizes SBI's charge card, the worth will be
"SBI".
For
Paytm Wallet, worth will be Wallet.
In
the event of UPI, this parameter won't be available in the reaction.
|
PAYMENTMODE
String(15)
|
The
installment mode utilized by client for exchange
Charge
card – CC
Check
card - DC
Net
banking - NB
UPI
- UPI
Paytm
wallet – PPI
Postpaid
- PAYTMCC
|
TXNTYPE
String(5)
|
The
estimation of this parameter is "Deal" for the installment.
|
REFUNDAMT
String(10)
|
Total
combined discount sum against this exchange. For instance for an exchange.
with request an incentive as INR 100, there has been two discounts of INR 20
and INR 30 truly, at that point REFUNDAMT will be INR 50.
|
Response Code:
RESPCODE
|
STATUS
|
RESPMSG
|
01
|
TXN_SUCCESS
|
Txn
Success
|
227
|
TXN_FAILURE
|
Your
installment has been declined by your bank. It would be ideal if you contact
your bank for any questions. On the off chance that cash has been deducted
from your record, your bank will illuminate us inside 48 hrs and we will
discount the equivalent.
|
235
|
TXN_FAILURE
|
Wallet
balance Insufficient, bankName=WALLET
|
295
|
TXN_FAILURE
|
Your
installment flopped as the UPI ID entered is inaccurate. If you don't mind
attempt again by entering a legitimate VPA or utilize an alternate strategy
to finish the installment.
|
334
|
TXN_FAILURE
|
Invalid
Order ID
|
400
|
PENDING
|
Transaction
status not affirmed at this point.
|
401
|
TXN_FAILURE
|
Your
installment has been declined by your bank. If it's not too much trouble contact
your bank for any inquiries. In the event that cash has been deducted from
your record, your bank will educate us inside 48 hrs and we will discount the
equivalent.
|
402
|
PENDING
|
Looks
like the installment isn't finished. If it's not too much trouble pause while
we affirm the status with your bank.
|
810
|
TXN_FAILURE
|
Txn
Failed
|
No comments:
Post a Comment