Initial queries directed from the merchant to Kount that do not originate from a call center environment.
Initial queries originating from a call center environment.
- IP Address must be hard coded as "10.0.0.1".
- If customer does not provide an e-mail address, use the value EMAL=noemail@Kount.com.
- PayPal is not a valid payment type for MODE=P.
Mode U Update call to Kount, does not cause a reevaluation of the transaction but will update what is displayed in the Agent Web Console. This update call does not count towards the number of RIS transactions purchased. Only certain fields can be updated with MODE=U calls. The PTYP field can only be updated if the initial post to Kount was PTYP=NONE
Update query made after an initial MODE=Q or P request and/or any MODE=U updates have been made. Updates to certain fields can be made and the transaction will be re-evaluated and return an updated RIS response to the merchant. These updates will be displayed in the Agent Web Console. This query will count towards the number of RIS transactions purchased. The same fields listed in the MODE=U section can be changed for MODE=X transactions except for PTYP which is not accepted by MODE=X.
This mode designates an error has occurred and is returned to the merchant in the RIS response.
RIS Inquiry Data Table
NOTE: All fields names for a RIS call must be UPPERCASE. They cannot be other case combinations such as sess, Merc, mOdE. However, the values for fields can be mixed case, such as SESS=UpperMixedCaseSessID95628.
|Name||Description||Character Limit||Valid Values||Required|
|AUTH||Authorization Status returned to merchant from processor. Acceptable values for the AUTH field are ’A’ for Authorized or ’D’ for Decline. In orders where AUTH=A will aggregate towards order velocity of the persona while orders where AUTH=D will decrement the velocity of the persona.||1||A or D||No|
|AVST||Address Verification System Street verification response returned to merchant from processor. Acceptable values are ’M’ for match, ’N’ for no-match, or ’X’ for unsupported or unavailable.||1||M (Match) N (Not a Match) X (Not Available)||No|
|AVSZ||Address Verification System Zip Code verification response returned to merchant from processor. Acceptable values are ‘M’ for match, ’N’ for no match, or ‘X’ for unsupported or unavailable.||1||M (Match) N (Not a Match) X (Not Available)||No|
|CVVR||Card Verification Value response returned to merchant from processor. Acceptable values are ’M’ for match, ’N’ for no-match, or ’X’ unsupported or unavailable.||1||M (Match)N (Not a Match) X (Not Available)||No|
|FRMT||Specifies the format of the RIS response if not using SDK, XML, JSON, YAML||4||SDK, XML, JSON, YAML||No|
|LAST4||Last 4 numbers of Credit Card Value||4||Numeric field must be 4 numbers||No|
|MACK||Merchants acknowledgement to ship/process the order. The MACK field must be set as ’Y’ if persona data is to be collected to strengthen the score.||1||Y or N||Yes|
|MERC||Merchant ID assigned to the merchant by Kount.||6||Numeric field must be 6 numbers||Yes|
|MODE||Specifies what mode type the RIS post is: MODE=Q MODE=P MODE=X MODE=U||1||Q, P, X, U||Yes|
|ORDR||Merchant’s Order Number||32||Alphanumeric field||No|
|PENC||RIS parameter for payment encoding.||KHASH||KHASH OR MASK||No|
|PTOK||PTOK value will replace Null value passed in original RIS Post.||32||Value to replace Null value passed in original RIS Post||No|
|PTYP||Payment Type submitted by merchant: PYPL BLML GDMP GOOG
- NOTE that PTYP must have been set to actual payment PTYP that will be updated within the initial RIS Post. PTOK must have been set to Null. If the PTYP is set to NONE no update can be performed.
|4||PYPL, BLML, GDMP, GOOG||No|
|RFCB||Refund/Chargeback status: R = Refund C = Chargeback||1||R (Refund) or C (Chargeback)||No|
|SESS||Unique Session ID. Must be unique over a 30- day span||32||Alphanumeric field; must be match original RIS Post||Yes|
|TRAN||Transaction ID required for update calls to Kount||12||Transaction ID generated by Kount, must match original RIS Post||Yes|
|VERS||Specifies version of Kount, built into SDK, must be supplied by the merchant if not using the SDK||4||Version of Kount being used||Yes|
NOTE: There are caveats to the PENC, PTOK and PTYP fields. Please contact your Client Success Manager for further details.