NET SDK all credit card information, by default, uses the KHASH encryption method where the credit card information is irreversibly hashed prior to transmission from the merchant to Kount. Output : BIN + 14 alpha-numeric characters. The SDK automatically sets this value prior to hashing the payment token for all payment types. The value of this field is the last four numbers/characters of the payment token. When the payment type is a credit card (optional for all other payment types), you must send data in the LAST4 input field. No credit card numbers, Paypal payment IDs, check numbers, Google Checkout IDs, Bill Me Later IDs, Green Dot MoneyPak IDs, gift card numbers, etc are transmitted in plain text. Net RIS SDK version 5.0.0+, all payment tokens are hashed (one-way encryption) prior to being transmitted to Kount. When using the SDK, KHASH and MASK are available. KAPT = Y means successful, KAPT = N means the process was unsuccessful. If the Kount Device Data Collector was used to collect customer information, the KAPT field can be checked to determine if this process was successful. All warnings are displayed in the response and if errors do occur the RIS response will be returned with a MODE = E. The merchant can then use the RIS response to automate the order management process by keying off of the AUTO field and can utilize any of the additional data returned for internal processing.Īn important use of the RIS response is the ability to view any warnings or errors that were made during the RIS post from the merchant. Each data field must be invoked by getter methods on the Response object from the SDK. The RIS response format is the same that was specified in the RIS request, with the default being named pairs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |