Performing Online Credit Card Authorizations
Overview: On-line credit card authorization allows you to send and receive the information required to authorize a credit card when the order is placed instead of when the pick slip is generated for the order.
In this topic: This chapter provides an overview of the on-line credit card authorization process and the required setup.
• Receiving a Credit Card Authorization During Order Entry
• What Credit Card Amount is Sent for Authorization?
• Hierarchy for Placing the Credit Card On Hold
• What Happens When a Credit Card is Approved?
• What Happens When a Credit Card is Declined?
• When Communication Failures Occur
• What Happens When an Undefined Response is Returned?
• Select Authorization Response Option Window
• Resending Credit Cards for Authorization
• Credit Card Authorization List
• Transmitting and Receiving Deposits
• On-line Authorization Process
• On-line Credit Card Authorization Setup
• Authorization Service Settings
• On-Line Authorization Async and Socket Server Job
Receiving a Credit Card Authorization During Order Entry
The system performs on-line authorization when you press F9 to accept an order after determining if the order should go on hold due to the credit card payment method.
Generic order interface: If you receive orders through the Generic Order Interface (Order API), the system performs on-line authorization after determining if the order should go on hold.
Batch order entry: If you are using batch order entry, the system performs on-line authorization when you enter 9 to accept a batch at the Work with Order Batches Screen or press F9 to accept a batch at the Select Customer Sold to for Order Screen.
1. The system determines if the order is eligible for on-line authorization. In order to receive a credit card authorization during order entry:
• the On-line Authorizations (B89) system control value must be set to Y.
• the order type defined for the order must be eligible for on-line authorizations (the On-line authorization field is set to 1 (on-line eligible and display window) or 2 (on-line eligible and do not display window).
• the order must have a credit card, Bill Me Later, stored value card, or debit (Switch) card payment method.
• the order must be in an open or suspended status.
See On-line Credit Card Authorization Setup for more information on setting up the required values for on-line authorization.
2. The system determines the amount to authorize.
What Credit Card Amount is Sent for Authorization?
• If the Online Auth Verification Only (I96) system control value is set to Y, the system processes online authorizations for $1.00 for the purpose of validating the card. During batch authorizations, the system authorizes the card for the shippable dollar amount and voids the online authorization for $1.00.
• If the Online Auth Verification Only (I96) system control value is set to N, the system looks at the setting of the Authorize Full Amount During Order Entry (G99) system control value to determine the amount sent for authorization.
The Authorize Full Amount During Order Entry (G99) system control value determines if the credit card is authorized for the full order amount or for the shippable amount on the order.
Authorize full amount... |
Authorize shippable amount... |
The system sends the entire dollar amount defined for the credit card for authorization. If the credit card is the only payment method... The amount to authorize is the order total. The order total is the sum of all charges on the order, including: merchandise, freight, additional freight, tax, handling, additional charges, GST and PST.
|
The system sends the dollar amount associated with what is shippable on the order, across all ship to customers, for authorization. If the credit card is the only payment method... This shippable dollar amount includes: • shippable merchandise amount, including drop ship items • tax associated with the shippable merchandise amount • total freight • total additional freight • total order level additional charges Note: The system sends the total freight and total additional freight for authorization, regardless of whether you are prorating freight charges (the Prorate Freight Charges (D39) system control value is set to Y). |
If the credit card is the catch-all payment method... The amount to authorize is the remaining dollar amount not associated with another payment method on the order. The system subtracts the amount applied to any other payment methods from the order total. order total - dollar amount associated with other payment methods = amount to authorize for this credit card |
If the credit card is the catch-all payment method... The amount to authorize is the remaining shippable dollar amount not associated with another payment method on the order. The system subtracts the amount applied to any other payment methods from the shippable dollar amount. shippable dollar amount - dollar amount associated with other payment methods = amount to authorize for this credit card |
|
Excluded from authorizations: • order lines with a future arrival date • order lines on backorder, canceled, closed, or sold out • reserved order lines that are coordinate grouped with an order line on backorder or with an order line with a future arrival date • orders in a held status |
Regardless of whether you are authorizing the full amount or the shippable amount... Included in authorizations: • express bill order lines • drop ship order lines • non-inventory order lines Deferred Billing If the credit card on the order is associated with a deferred pay plan, the system: • sends an authorization for $1.00 if the Authorize full amount field for the pay plan is set to N. • sends an authorization for the dollar amount available for authorization if the Authorize full amount field for the pay plan is set to Y. Installment Billing If the credit card on the order is associated with an installment pay plan, the system: • sends an authorization for the first installment amount if the Authorize full amount field for the pay plan is set to N. • sends an authorization for the dollar amount available for authorization if the Authorize full amount field for the pay plan is set to Y. |
|
If more than one credit card is sent for authorization: The system sends for authorization the credit card defined with a dollar amount, then sends the catch-all credit card for authorization. |
|
Credit cards requiring authorizations less than the automatic authorization dollar threshold: When you perform online authorization, the system determines if the authorization amount qualifies for automatic authorization.
• If the credit card amount to authorize is less than the dollar amount defined in the $ Threshold for Automatic Authorization # Assignment (K36) system control value and you have defined an authorization number in the Authorization Number for Authorizations Under $ Threshold (K37) system control value, the system does not send the credit card to the service bureau for authorization and instead assigns the authorization number defined in the Authorization Number for Authorizations Under $ Threshold (K37) to the credit card.
• If the $ Threshold for Automatic Authorization # Assignment (K36) or Authorization Number for Authorizations Under $ Threshold (K37) system control value is blank, the credit card amount to authorize is less than $1.00, and you have defined an authorization number in the Authorization Number for Authorizations Under $1.00 (I08) system control value, the system does not send the credit card to the service bureau for authorization and instead assigns the authorization number defined in the Authorization Number for Authorizations Under $1.00 (I08) system control value to the credit card.
Credit cards requiring authorizations less than the reserve dollar threshold: If the Authorize Full Amount During Order Entry (G99) system control value is set to N and the authorization amount does not qualify for automatic authorization (see above), the system determines if the authorization amount meets the reserve dollar threshold.
• If the credit card amount to authorize is less than the amount defined in the Online Auth Reserve $ Threshold (L74) system control value and part of the order is not shippable, the system does not send the credit card to the service bureau for authorization. The system will send the credit card to the service bureau during batch authorization.
• If the credit card amount to authorize is less than the amount defined in the Online Auth Reserve $ Threshold (L74) system control value and all of the order is shippable, the system sends the credit card to the service bureau for authorization.
• If the credit card amount to authorize is equal to or greater than the amount defined in the Online Auth Reserve $ Threshold (L74) system control value, the system sends the credit card to the service bureau for authorization.
Bill Me Later orders: When you process an online authorization for an order containing a Bill Me Later pay type, the system always authorizes the pay types on the order for the full amount, regardless of the setting of the Authorize Full Amount During Order Entry (G99) system control value and Online Auth Verification Only (I96) system control value; see Performing Online Authorization for a Bill Me Later Order.
3. The system sends the authorization amount to the authorization service. If there is an amount to authorize for the credit card, the system calls the Get On-Line Authorization program. This program manages communication between CWDirect and the authorization service.
See Authorization Request XML Message (CWAuthorizationRequest) for the information sent to the authorization service.
4. The authorization service sends back a response. The authorization service sends a response to the Get On-Line Authorization program.
There are 3 types of responses you can receive from the authorization service.
• R = an authorization response is received, such as declined or approved
• T = the program timed out before an authorization response was received
• U = an undefined response
Additionally, if an authorization response is received, the authorization service sends back an authorization response code, AVS response code (if performing address verification), CID response code (if performing credit card identification verification), authorization code, and date. See Authorization Response XML Message (CWAuthorizationResponse) for the information received from the authorization service.
Vendor response settings: If a pop up window message has been defined for the vendor response received, the system displays the Select Authorization Response Option Window in order entry. Also, if a hold reason code has been defined for the vendor response received, the system places the order on hold.
Relate stored value cards: When using the Relate Stored Value Card Integration, if the Relate stored value card is the only payment on the order and the amount authorized for the card is less than the order total, the system updates the amount for the card with the amount authorized and displays the message Insufficient balance on card - please add another payment. In order to accept the order, you must add another payment to the order to cover the amount of the order that is not covered by the Relate stored value card. Example: If the order total is 500.00 and the amount authorized for the Relate stored value card is 236.20, the system updates the amount for the card to 236.20 and requires another form of payment to cover the remaining 289.55 balance on the order.
Hierarchy for Placing the Credit Card On Hold
The credit card pay type may be placed on hold if the credit card is not approved, the AVS verification fails, or the CID verification fails.
The system uses this hierarchy to determine if the credit card pay type should go on hold:
• Authorization response has a hold reason defined: If the credit card charge is declined (not authorized), the credit card may be placed on hold (based on the value in the Hold reason field in the Vendor Response file). The order header is also placed on AT (declined credit card) hold. You must take the order header and credit card pay type off of hold through the Release Held Orders function and resend for authorization or cancel the order.
• AVS response has a hold reason defined: If the credit card charge is approved (authorized) but the credit card fails the address verification check, the authorization may be placed on hold (based on the value in the Hold reason field in the Vendor Response file). The order header is also placed on AT (declined credit card) hold. You must contact the customer and obtain correct address information, then take the order header and credit card pay type off of hold through the Release Held Orders function and resend for authorization or cancel the order.
• Card security identification response has a hold reason defined: If the credit card charge is approved (authorized) and passes the address verification check, but the credit card fails the credit card security identification check, the credit card pay type may be placed on hold (based on the value in the Hold reason field in the Vendor Response file). The order header is also placed on AT (declined credit card) hold. You must contact the customer to verify credit card ownership, then take the order header and credit card pay type off of hold through the Release Held Orders function and resend for authorization or cancel the order.
For more information: See Defining Vendor Response Codes and Customer Service Establishing Cancel Reason Codes (WCNR).
What Happens When a Credit Card is Approved?
When a credit card is approved during order entry, the system:
• during order entry, displays the Select Authorization Response Option Window if a vendor response pop up window message has been defined and the On-line authorization field for the order type is set to 1 (on-line eligible and display window). The message should indicate the credit card has been approved. From this window, you can accept the order or return to the order to make any corrections. If a credit card has been approved, you should accept the order.
• places the order on hold if a hold reason code has been defined for the vendor response. Typically, if an authorization is approved, the order is not placed on hold. However, if the credit card is approved but fails address verification or card identification verification, you may want to place the order on hold.
• once you accept the order, you return to the Select Customer Sold To For Order Screen, or the Customer Selection Screen if you are a CTI user.
• processes any end-of-order updates and sends the order to the Order Async.
• creates a record in the On-Line Authorization file indicating the order number, that the credit card has been approved, the dollar amount authorized, the transaction sequence number, and the authorization number. The status for this authorization is *UPDT, indicating the on-line authorization has completed.
• creates a record in the Authorization History file indicating the credit card has been approved, the authorization number, the date the credit card was authorized, and the dollar amount authorized. If you reject an order after the credit card has been approved, the system removes the record in the Authorization History file. You can review authorization history at the Display Authorization History Screen.
• creates a record in the Void Authorization file indicating the order number and the dollar amount eligible for void. If you reject an order after the credit card has been approved, the system removes the record from the Void Authorization file.
AVS response: If the credit card charge is approved (authorized) but the order fails the address verification check and receives an AVS response that has a hold reason code, the system:
• places the order on AT hold.
• places the credit card payment method on the order on AV (AVS) hold.
• creates an order transaction history message indicating the credit card was declined: SYS HLD - DECLINED CREDIT CARD.
• updates the record in the On-Line Authorization file indicating the credit card failed AVS. The OLA AVS result field is updated with the AVS response received from the authorization service. You can review the response at the Authorization History Details Window.
• updates the record in the Authorization History file indicating the credit card failed AVS. The AUH status field is updated to O (authorized but not used) and the AVS response field is updated with the AVS response received from the authorization service. You can review the status of the credit card and the AVS response at the Authorization History Details Window.
You must contact the customer and obtain correct address information, then take the order off of hold through the Release Held Orders function and resend for authorization.
If the authorization has not yet expired and the transaction passes AVS, the system updates the credit card authorization record from an O (authorized but not used) status to an A (approved) status. If the authorization has expired, the system updates the credit card authorization record from an O (authorized but not used) status to a D (declined) status and resends the credit card for authorization and address verification.
Note: The system only performs address verification if the Address verification field for the authorization service is set to Y; see Address Verification Service (AVS).
Card security identification response: If the credit card charge is approved (authorized) but the order fails the credit card security check and receives a card security identification response (CID, CVV2, CVC2) that has a hold reason code, the system:
• places the order on AT hold.
• places the credit card payment method on the order on CF (credit card fraud) hold.
• creates an order transaction history message indicating the credit card was declined: SYS HLD - DECLINED CREDIT CARD.
• updates the record in the On-Line Authorization file indicating the credit card failed card security. The OLA vendor response 2 field is updated with the card security response received from the authorization service. You can review the response at the Authorization History Details Window.
• updates the record in the Authorization History file indicating the credit card failed card security. The AUH status field is updated to O (authorized but not used) and the Vendor response 2 field is updated with the card security response received from the authorization service. You can review the status of the credit card and the card security response at the Authorization History Details Window.
You must contact the customer to verify credit card ownership, then take the order off of hold through the Release Held Orders function and resend for authorization.
If the authorization has not yet expired and the transaction passes card security identification, the system updates the credit card authorization record from an O (authorized but not used) status to an A (approved) status. If the authorization has expired, the system updates the credit card authorization record from an O (authorized but not used) status to a D (declined) status and resends the credit card for authorization and card security identification.
Note: The system only performs credit card security identification if the card security presence and optionally card security value are included in the authorization transaction passed to the authorization service; see Credit Card Security Service (CID, CVV2, CVC2).
What Happens When a Credit Card is Declined?
When a credit card is declined during order entry, the system:
• during order entry, displays the Select Authorization Response Option Window if a vendor response pop up window message has been defined and the On-line authorization field for the order type is set to 1 (on-line eligible and display window). The message should indicate the credit card has been declined and any action you should take to correct the decline or inform the customer. From this window, you can accept the order or return to the order to make any corrections.
• places the order on hold if a hold reason code has been defined for the vendor response.
• once you accept the order you return to the Select Customer Sold To For Order Screen, or the Customer Selection Screen if you are a CTI user.
• processes any end-of-order updates and sends the order to the Order Async.
• creates a record in the On-Line Authorization file indicating the order number, that the credit card has been declined, the dollar amount submitted for authorization, and the transaction sequence number. The status of this authorization is *UPDT, indicating the on-line authorization has been completed.
• creates a record in the Authorization History file indicating the credit card has been declined, the reason why the credit card was declined, the date the credit card was declined, and the dollar amount submitted for authorization. If you reject the order after the credit card has been declined, the system removes the record from the Authorization History file. You can review authorization history at the Display Authorization History Screen.
You can send the credit card up for authorization again during order maintenance, using the Performing Batch Authorization (SATH) menu option, or during pick slip generation if the Batch/on-line field for the authorization service contains a C (on-line and batch authorizations).
When Communication Failures Occur
Communication failures can occur if the on-line authorization socket server is inactive, the on-line authorization async is inactive, or the system times out before a response is received. If communication failures occur and you do not receive a response from the authorization service, the system:
• does not display the Select Authorization Response Option Window since a vendor response was not received.
• accepts the order and returns you to the Select Customer Sold To For Order Screen, or the Customer Selection Screen if you are a CTI user.
• processes any end-of-order updates and sends the order to the Order Async.
• creates a record in the On-Line Authorization file. The status of this authorization is:
• *RDY, indicating on-line authorization has not been performed because the on-line authorization socket server was inactive.
• *SENT, indicating the on-line authorization socket server became inactive after the credit card is sent to the authorization service for authorization.
• *RCVD, indicating the on-line authorization async is inactive when a response is received from the authorization service. The authorization does not complete processing until the Async is active. Once the on-line authorization Async is active, the system updates the status of the authorization to *UPDT.
• creates a record in the Authorization History file indicating the credit card is waiting for authorization, the date the credit card was sent for authorization, and the dollar amount waiting for authorization.
The amount of time the system waits for an authorization is defined in the Response time field for the authorization service.
See Resending Credit Cards for Authorization for a list of options you can use to receive an authorization response.
What Happens When an Undefined Response is Returned?
When an undefined response is returned, the system:
• does not display the Select Authorization Response Option Window since this vendor response has not been defined for the authorization service.
• places the order on AVS hold.
• accepts the order and returns you to the Select Customer Sold To For Order Screen, or the Customer Selection Screen if you are a CTI user.
• processes any end-of-order updates and sends the order to the Order Async.
• creates a record in the On-Line Authorization file indicating the order number, that the credit card is waiting for authorization, the dollar amount waiting for authorization, and the transaction sequence number. The status of this authorization is *RDY, indicating on-line authorization has not been performed.
• creates a record in the Authorization History file indicating the credit card is waiting for authorization, the date the credit card was sent for authorization, and the dollar amount waiting for authorization.
See Resending Credit Cards for Authorization for a list of options you can use to receive an authorization response.
Select Authorization Response Option Window
Purpose: Use this window to review the response received from the authorization service and any messages defined for this vendor response.
Once you review the message, you can accept the order or return to the order to make any corrections or reject the order.
Typically, a vendor response pop up window message is defined for a vendor response indicating a declined authorization, declined address verification, or declined card identification verification.
How to display this screen: This window displays when you press F9 to accept an order in order entry if:
For non-prepaid pay types:
• the dollar amount defined for the credit card payment method on the order was sent up for authorization and received a response, and
• the On-line authorization field for the order type on the order is set to 1 (on-line eligible and display window), and
• the Pop up window messages field for the vendor response returned by the authorization service contains text.
Note: The Pop up window messages # 1 field must contain text in order to display this window. If you define text in the Pop up window messages # 2 - # 4 fields and not in the Pop up window messages # 1 field, this window will not display.
For prepaid pay types:
• the dollar amount defined for the prepaid payment method on the order was sent up for authorization and received a response, and
• the On-line authorization field for the order type on the order is set to 1 (on-line eligible and display window).
This window displays for each credit card payment method on the order that is sent up for authorization and meets the criteria above.
What message displays? You can receive a response from the authorization service for the authorization, address verification (AVS), and credit card security identification (CID, CVV2, CVC2). If you receive a response for the authorization, AVS verification, and card security identification, the system uses the following hierarchy to determine the pop up window message that displays in the Select Authorization Response Option window:
• Authorization response has a message defined: the message associated with the authorization response displays in the Select Authorization Response Option window.
• AVS response has a message defined: if the authorization response does not have a message defined, the message associated with the AVS response displays in the Select Authorization Option window.
• Card security identification response has a message defined: if the authorization response and AVS response do not have a message defined, the message associated with the card security response displays in the Select Authorization Option window.
Batch order entry: This window does not display if you are performing on-line credit card authorization during batch order entry.
Order maintenance: The Select Authorization Response Option window displays if you are performing on-line credit card authorization during order maintenance. You can authorize a credit card during order maintenance by entering 6 next toa credit card payment method.
Select Authorization Response Option
Order # . . . 1443 Pay Type . . LITLE VISA Credit card # 1711000101590247 Exp date 812 Auth Amt: 21.25 Issue # Start Date 0 Prepaid Avail Balance: 20.00 000 APPROVED
This prepaid card is not reloadable.
F9=Accept Order F11=Edit Order |
Field |
Description |
Order # |
The order number containing the credit card payment method that received this authorization response. Numeric, 8 positions; display-only. |
Pay type |
The description of the credit card payment method that received the authorization response containing this message text. Alphanumeric, 30 positions; display-only. |
Credit card # |
The credit card number defined for the credit card payment method used on the order. If you use Credit Card Tokenization, this number may be a token rather than the actual credit card number. If you do not have authority to the Display Full Credit Card Number (B14) secured feature, the credit card number displays in the format specified at the Credit Card Number Layout Screen for the associated pay type. For example, 4788********1443 may display instead of the entire credit card number. See Credit Card Number Format for an overview. Alphanumeric, 20 positions; display-only. |
Exp date (credit card expiration date) |
The date this credit card is no longer valid. Numeric, 4 positions (MMYY format); display-only. |
Auth amt |
The amount sent for authorization for this credit card. Numeric, 10 positions with a 2-place decimal; display-only. |
Issue # |
An incremental issue number, assigned by some banks when they replace a card because it is lost or stolen. Debit cards might require a start date, an issue number, both, or neither. The Require issue # flag for the pay type controls whether an issue number is required or optional. Alphanumeric, 2 positions; display-only. |
Start date |
The first date when the card is effective. the Require start date flag for the pay type controls whether the start date is required or optional. Numeric, 4 positions; display-only. |
Prepaid avail bal |
The available balance of the prepaid card used on the order. You can use this balance to inform the customer and determine whether the prepaid card should be used with deferred or installment billing plans. Numeric, 9 positions with a 2-place decimal; display-only. |
Vendor response pop up window messages # 1 - # 4 |
The message text defined in the Pop up window messages # 1 - # 4 fields for the vendor response you received from the authorization service. This message text should indicate whether the credit card has been approved or declined and any action that you should take to correct any problems and inform the customer. Alphanumeric, four 40-position fields; display-only. |
Reloadable |
Defines whether additional funds can be added to the prepaid card used on the order. This prepaid card is not reloadable displays if additional funds cannot be added to the prepaid card. This prepaid card is reloadable displays if additional funds can be added to the prepaid card. |
Screen Option |
Procedure |
Accept the order |
Press F9. The system returns you to the Select Customer Sold To For Order Screen or the Customer Selection Screen if the operator placing the order is a CTI user, and processes the order through the Order Async. |
Return to the order to make any corrections or reject the order |
Press F11. The system returns you to the Work with Order/Recap Screen or the Enter Payment Method Screen where you can make any corrections or reject the order. |
Resending Credit Cards for Authorization
If you did not receive a response from the authorization service during order entry or the credit card was declined in order entry, you can resend the credit card for authorization using one of the following options.
• Use option 6 (perform authorization on-line) against the credit card at the Enter Payment Methods Screen in order maintenance. The system sends the credit card for authorization, waits for a response as in order entry, and displays the Select Authorization Response Option Window if pop up window message text was defined for the vendor response.
• Use the Performing Batch Authorization (SATH) menu option to send credit cards associated with a selected ship via for authorization using a leased line for communication.
• If the authorization service for the credit card matches the authorization service in the Authorization Service for Authorization Inquiries (K29) system control value, the system sends an authorization inquiry request to the service bureau before performing batch authorization in order to receive authorizations for credit cards that did not receive an authorization during order entry. See Batch Authorization Inquiry Processing.
• Perform batch authorization during pick slip generation or drop ship processing if the Batch/on-line field for the authorization service contains a C (on-line and batch authorizations). See Batch Authorization Processing.
You can generate pick slips for orders that contain pre-paid payment methods, such as cash or check, and/or credit cards that have received an approved authorization by setting the Preauthorized orders only field in the pick generation template to Y.
If you try to generate pick slips for orders that contain credit cards that have not been authorized with the Preauthorized orders only field set to Y and the Use Auto Authorization Interface (C14) system control value is set to Y, the system will not send the credit cards up for authorization and will not generate pick slips.
Note: If you generate pick slips for preauthorized orders only and records exist in the Authorization History file in an S (sent) status, the system updates the records to a D (decline) status. The next time you generate pick slips with the Preauthorized orders only field set to N, the system sends orders associated with records in the Authorization History file in a D status up for authorization.
Receiving authorizations during pick slip generation: If the credit card has not yet received an approved authorization, you can resend the credit card for authorization during pick slip generation if the Preauthorized orders only field in the pick generation template is set to N and the Batch/on-line field for the authorization service is set to C (batch and on-line authorization). The authorizations can be transmitted to the authorization service using a leased line or a dial-up connection. See Reviewing Authorizations for more information on receiving authorizations during pick slip generation.
Credit Card Authorization List
The Online Credit Card Authorization Listing is a report you can use to review credit cards that have been authorized, declined, or sent for authorization for a specific date range.
You can generate this report by:
• defining selection criteria at the Authorization Listing Screen and pressing F9.
• sending credit cards for authorization using the Performing Batch Authorization (SATH) menu option.
Note: The system generates a similar report when you authorize credit cards during pick slip generation; see Credit Card Authorization Listing.
Transmitting and Receiving Deposits
After you obtain an authorization for a credit card charge, you can generate a pick slip for the order, ship the order to the customer, and charge the credit card for the shipment. At this point, you use Processing Auto Deposits (SDEP) to transmit the deposit information to a deposit service for settlement.
On-line Credit Card Authorization Setup
Purpose: Before you can receive on-line credit card authorizations in your company, you must perform the necessary setup. Information requiring creation and setup includes:
• system control values
• number assignment value
• authorization service settings, including response codes and currency codes
• order types eligible for on-line credit card authorization
• credit card payment type settings
• on-line authorization async job and socket server job settings for the authorization service
• Online CC Auth Process integration layer job settings
• optionally, pick slip generation template to generate pick slips for orders that contain pre-authorized credit cards
System Control Value |
Description |
Set this field to Y to indicate you will be performing on-line credit card authorizations. If this field is set to N or blank, you will not be able to authorize credit cards in order entry or order maintenance. |
|
Set this field to Y to indicate you will send an order up for authorization for the full order amount. Enter N or leave this field blank to indicate you will send an order up for authorization for the shippable order amount. |
|
Set this field to Y to indicate you want the system to process online authorizations for $1.00 for the purpose of validating the card. During batch authorizations, the system authorizes the card for the shippable dollar amount and voids the online authorization for $1.00. If this field is set to N or blank, the system looks at the Authorize Full Amount During Order Entry (G99) system control value to determine the amount sent for authorization. |
|
Enter the shippable dollar amount the system uses to determine whether to process an online authorization for the credit card payment on the order. The system evaluates this system control value after determining whether the authorization amount qualifies for automatic authorization, based on the settings of the $ Threshold for Automatic Authorization # Assignment (K36), Authorization Number for Authorizations Under $ Threshold (K37), and Authorization Number for Authorizations Under $1.00 (I08) system control values. |
See Authorization/Deposit Setup for additional system control values related to authorization.
The number assignment Transaction Sequence # assigns the next available number to the credit card authorization.
Authorization Service Settings
When you are setting up the authorization service, please note these required settings:
• Industry code: enter your DBA number.
• Batch/on-line: set to I (on-line) to perform only on-line credit card authorizations; set to C (on-line or batch) to perform both on-line credit card authorizations and batch credit card authorizations.
• Response time: set the number of seconds the system waits to receive a response from the authorization service before continuing to process the order.
• Paytype cross reference (option 8 at the Work with Authorization Services Screen): Create a cross-reference for each pay type code for which you wish to receive on-line credit card authorization, using the vendor pay code information supplied by the service bureau.
• Currency cross reference (option 12 at the Work with Authorization Services Screen): Create a cross-reference for each currency code you will use on orders receiving on-line credit card authorizations, using the vendor currency code information supplied by the service bureau.
• Vendor responses (option 9 at the Work with Authorization Services Screen): Optionally, you can define Vendor response pop up window messages. The messages display in a pop up window in order entry when a credit card that was sent up for authorization is declined. You can enter up to four 40-position lines of message text. Set up vendor responses for authorizations, AVS (if you are performing address verification), and CID (if you are performing credit card identification).
You define whether an order type is eligible for on-line authorizations and if the order type will display a window during order entry when a response is received from the authorization service, based on the value defined in the On-line authorization field:
• 1 indicates the order type is eligible for on-line authorizations and the Select Authorization Response Option Window displays.
• 2 indicates the order type is eligible for on-line authorization and the Select Authorization Response Option Window does not display.
• 3 indicates the order type is not eligible for on-line authorization.
Each credit card pay type eligible for on-line authorization should have a service bureau that supports online authorization set up as its authorization and deposit service. See Accounts Payable Working with Pay Types (WPAY) for more information on setting up pay types.
If you wish to generate pick slips only for orders that contain pre-paid payment methods and/or credit cards that have received an authorization, you can create a pick slip generation template with the Preauthorized orders only field set to Y.
On-Line Authorization Async and Socket Server Job
First Data Merchant Services and Paymentech Online Processing Revision 4.0 processes online authorizations using the On-Line Authorization async and socket server job; this job must be started in Working with Socket Server Jobs (SOCK). The on-line authorization socket server manages communication between CWDirect and the authorization service, waiting for new credit card information to send and “listening” for credit card authorization responses to receive.
Note: You must purchase the IBM Socket Client software and a leased line in order to have a direct connection to the authorization service. Contact your MICROS representative.
This table displays the required values for the Socket Server job if you are using Paymentech. If you wish to use an authorization service other than Paymentech, a new socket server job will need to be created with the appropriate program names.
Field |
Value |
Server |
PMT |
Description |
The description of the socket server job. Example: Paymentech On-Line Authorization. |
Connection ID |
The job name of the socket server outbound and inbound programs located in the subsystem. Example: If the connection ID is A123456, the: • incoming data program is named A123456IN • outgoing data program is named A123456OUT |
Port number |
Paymentech provides this value. |
Outbound program |
AAR0218 |
Outbound dataqueue |
AUTHOUTDTQ |
Outbound dataqueue length |
221 |
Inbound program |
AAR0217 |
Inbound dataqueue |
AUTHINDTQ |
Inbound dataqueue length |
61 |
Dataqueue library |
This is based on the version and environment you are using to perform on-line authorizations. Example: CWM40QDTA |
Async job name |
AUTH_ASYNC |
Async program name |
AAR0216 |
# of inbound async jobs |
3 (default) Increase this number to handle larger volumes of orders. |
Job description |
QZRDDCLT_Q |
IP address |
198.147.142.176 |
Online CC Auth Process Integration Layer Job
Paymentech Online Processing Revision 6.0 and all other service bureaus that support online authorization process online authorizations via CWIntegrate using the Online CC Auth Process integration layer job in Working with Integration Layer Processes (IJCT).
When active, the Online CC Auth Process integration layer job generates an Authorization Request XML Message (CWAuthorizationRequest) and sends the message to the job’s outbound MQ queue. Once the service bureau sends back a response, the integration layer job receives the Authorization Response XML Message (CWAuthorizationResponse) in the inbound MQ queue.
| Defining Authorization Service Countries | Contents | SCVs | Search | Glossary | Reports | Solutions | XML | Index | Performing Batch Authorization (SATH) |
SO04_09 CWDirect 18.0.x 2018 OTN