Incorrect Message Generated When Manually Approving A Check (Doc ID 2133553.1)

Last updated on JULY 24, 2017

Applies to:

Oracle Retail Point-of-Service - Version 13.4.1 and later
Information in this document applies to any platform.

Symptoms

When manually approving a check, Point of Service (POS) application incorrectly builds a new request message which includes an Authorize Check Call Reference Request with Message Type 'D' sent to PinComm -> SAFTOR followed by the payment switch. When the payment switch receives this message, it does not recognize the message type and responds with message "INVALID MESSAGE TYPE".

Steps to Reproduce:

1. Run a check authorization requiring a manual approval.
2. Enter any value for the approval number.
3. Examine the PinComm and SAFTOR logs , find that a message which includes an Authorize Check Call Reference Request with Message Type 'D' is being sent to PinComm and an error is thrown in Pincomm. This message which includes an Authorize Check Call Reference Request with Message Type = 'D' should NOT be sent to Pincomm/SAFTOR when a check is manually approved.

======================
Request
------------
sgJK000010010080
AUTH_CODE=666 (Assumed entered "666" as Referral Code)

Response
---------------
sgJK000010010080
RESP_MESS=INVALID MESSAGE TYPE
AUTH_CODE= (AUTH_CODE is empty from the PinComm/SAFTOR response because Request was not approved)

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms