Defining Authorization Services (WASV)
Purpose: Use the Work with Authorization Services menu option to:
-
define the service bureaus that you use, such as:
-
Authorization services, to authorize charges against a credit card or stored value card.
-
Authorization/Deposit services, to authorize card charges and receive deposit amounts.
-
Deposit services, to provide settlement for card payments.
-
-
identify the type of service the service bureau performs
-
define the parameters that identify your company to the service bureau
-
define the information necessary to connect, transmit, and receive data to and from the service, such as:
-
country codes
-
valid pay types
-
response codes (vendor responses, AVS responses, and CID responses)
-
currency codes
-
merchant IDs for individual entities within your company
-
whether the order originated as an internet order
-
Some of the information required to establish a service bureau on your system is provided by the service bureau. For example, each service bureau will assign you a unique password.
You can use the same service bureau to process your authorizations and deposits, or you can use one service for authorizations and another for deposits.
Important:
Use the Payment Configurations option in Modern View to configure or work with any payment processing through EFTConnect. You would use Work with Authorization Services in Classic View only for other authorization services, such as for stored value cards (gift cards). You cannot create, change, or delete an authorization service that uses EFTConnect through the Work with Authorization Services option in Classic View.
In this topic:
Deferred/Installment Pay Plans
Deferred or installment pay plans allow you to process deposits against orders at various intervals after you bill the order shipment. For example, you could offer “no payment for 60 days” or “four easy payments” to your customers.
In order to set up deferred or installment pay plans, you must have the Deferred and Installment Billing (F51) system control value must be selected. See Deferred/Installment Billing Overview for more information on deferred and installment pay plans and how to set them up in Order Administration.
Identifying Internet Orders
An internet order is determined in one of two ways:
-
If using the E-Commerce Interface the system loads an I in the Internet field on the order header when the order is created in Order Administration.
-
An order is considered an internet order if the order type on the order matches the E-Commerce Order Type (G42) system control value.
-
Mail = Mail order.
-
Phone = Telephone order.
-
Internet = Web order.
To determine where the order originated, the system:
-
looks at the value in the Internet order field in the Order Header table. If this field is set to I, the order is a web order.
-
determines if the order type for the order matches the E-Commerce Order Type (G42) system control value. If the order type matches, the order is a web order.
-
looks at the Forecasting order category field in the Order Type table. If this value is 1, the order is a mail order. If this value is 2, the order is a phone order.
Work with Authorization Services Screen
How to display this screen: Enter WASV in the Fast path field at the top of any menu screen or select Work with Authorization Services from a menu.
Field | Description |
---|---|
Code |
The code to identify the service bureau. Enter a full or partial code and select OK to display service codes in alphanumeric order, starting with your entry. Alphanumeric, 3 positions; optional. |
Application |
The type of activity performed by the service bureau. Valid values are:
Optional. |
Description |
The name of the service bureau. Alphanumeric, 30 positions; optional. |
Merchant |
The account number assigned by the service bureau to identify transmissions to/from your company. This is the default ID number; you can also specify separate ID numbers for each entity in your company, and/or to use for orders using deferred or installment billing. Alphanumeric, 20 positions; optional. |
Screen Option | Procedure |
---|---|
Change an authorization service record |
Select Change for a service to advance to the Change Authorization Services Screen. At this screen you can change any information except the Service code. See the First Create Authorization Services Screen for field descriptions. Important: You cannot use this option to change an existing authorization service using EFTConnect. Use the Payment Configurations option in Modern View instead. |
Delete an authorization service record |
Select Delete for a service to delete it. Important: You cannot use this option to delete an existing authorization service using EFTConnect. Use the Payment Configurations option in Modern View instead. |
Display an authorization service record |
Select Display for a service to advance to the Display Authorization Services Screen. You cannot change any information at this screen. See the First Create Authorization Services Screen for field descriptions. |
Work with country codes |
Select Country for a service to add, change or delete the country codes recognized by the service bureau; see Defining Authorization Service Countries. |
Work with vendor paytype codes |
Select Paytypes for a service to add, change, delete or display the pay type codes recognized by the authorization service. See Defining Vendor Paytype Codes. |
Work with vendor responses |
Select Responses for a service to add, change, display or delete the response codes you receive from the service and the actions to take for each. See Defining Vendor Response Codes. |
Work with merchant ID overrides based on entity |
Select Merchant ID Override for a service to add, change, or delete merchant ID overrides by entity. See Defining Merchant ID Overrides. |
Work with currency codes |
Select Currency for a service to add, change, or delete cross-references between the currency codes used in your company and by the authorization service. See Defining Authorization Service Currencies. |
Work with external authorization service settings |
Select External Service to advance to the Work with External Authorization Service Screen. External Authorization Service Access (B25) authority is required. |
Create an authorization service |
Select Create to advance to the First Create Authorization Services Screen. Important: You cannot use this option to create an existing authorization service using EFTConnect. Use the Payment Configurations option in Modern View instead. |
First Create Authorization Services Screen
Purpose: Use this screen to define a service bureau on your system. The Authorization Service record contains information that identifies your company to the service bureau and the parameters that you must include in the transmission to the service bureau.
Each service bureau requires its own information. Not all fields are applicable for each service.
Important:
You cannot use this screen to create a new authorization service using EFTConnect. Use the Payment Configurations option in Modern View instead.
How to display this screen: Select Create at the Work with Authorization Services Screen.
Field | Description |
---|---|
The code to identify the service bureau. Foreign credit cards: In order to process foreign credit cards separately at billing, you must define a deposit service with a code of PRE, and then define PRE as the deposit service in the Pay Type table. See Processing Auto Deposits (SDEP) for more information on setting up a different process for foreign credit cards. Point-to-Point communication: If you are using point-to-point communication, the Service code must be a specific value for the integration:
Alphanumeric, 3 positions. Create screen: required. Change screen: display-only. |
|
The type of activity performed by the service bureau. Valid values are:
Note: PayPal should have the Application type set to Auth/Deposit. Required. |
|
The account number assigned by the service bureau to identify transmissions to/from your company. This ID is a default. You can also identify merchant IDs to use for depositing deferred or installment pay plans (as opposed to regular deposits) below. Similarly, you can set up overrides for different entities in your company, including deferred or installment overrides. See Defining Merchant ID Overrides. Note: You can enter upper and lower case letters in this field. Alphanumeric, 20 positions; optional. |
|
A description that identifies your company's product line or the type of service performed. Alphanumeric, 20 positions; optional. |
|
Deferred merchant ID |
The account number assigned by the service to identify transmission of deferred pay plan transactions for deposit. See Deferred/Installment Billing Overview for more information on deferred and installment billing, and see Processing Auto Deposits (SDEP) for more information on processing deposits. You can also set up overrides for different entities in your company, including deferred or installment overrides. See Defining Merchant ID Overrides. Alphanumeric, 20 positions; optional. |
Installment merchant ID |
The account number assigned by the service to identify transmission of installment pay plan transactions for deposit. See Deferred/Installment Billing Overview, and see Processing Auto Deposits (SDEP). You can also set up overrides for different entities in your company, including deferred or installment overrides. See Defining Merchant ID Overrides. Alphanumeric, 20 positions; optional. |
The service bureau assigns values to the following fields: |
|
Signon |
A code required to sign on to the service bureau. Case-sensitive. Alphanumeric, 10 positions; optional. |
Receiving code |
A code that identifies your company to the service bureau. Alphanumeric, 10 positions; optional. |
Password |
A password required by the service bureau. Case-sensitive. Alphanumeric, 10 positions; optional. |
Start up information |
Startup text that identifies your company to the service bureau. Alphanumeric, 10 positions; optional. |
A code required to sign on to the service bureau. Separate fields allow you to define a presenter’s ID for both batch authorization and deposit transactions; if you use the same port number for both batch authorization and deposit transactions, define the presenter’s ID in the first field. Alphanumeric, 10 positions; optional. |
|
PID password Auth / Deposit |
A password required to sign on to the service bureau. Separate fields allow you to define a PID password for both batch authorization and deposit transactions; if you use the same port number for both batch authorization and deposit transactions, define the PID password in the first field. Alphanumeric, 10 positions; optional. |
A code required to sign on to the service bureau. Separate fields allow you to define a submitter’s ID for both batch authorization and deposit transactions; if you use the same port number for both batch authorization and deposit transactions, define the submitter’s ID in the first field. Alphanumeric, 10 positions; optional. |
|
SID password Auth / Deposit |
A password required to sign on to the service bureau. Separate fields allow you to define a SID password for both batch authorization and deposit transactions; if you use the same port number for both batch authorization and deposit transactions, define the SID password in the first field. Alphanumeric, 10 positions; optional. |
Sub code |
A code required to sign on to the service bureau. Alphanumeric, 10 positions; optional. |
Exclude from FPO (Exclude from flexible payment option) |
Indicates whether to exclude orders associated with this service bureau from a deferred or installment pay plan. If an order includes any pay type whose authorization service has this field selected, the order is not eligible for a pay plan. Valid values are:
See Deferred/Installment Billing Overview for information on how the system determines whether an order is eligible for a pay plan in order entry. |
Defines whether any unused portion of an authorization should be voided at deposit time for:
Valid values are:
See Void Unused Authorization After Initial Deposit for processing details. Important: Your end payment processor must support split shipments for you to set this flag to N. Stored value card pay types when not using the External Payment Service: The setting of the Retain Unused Stored Value Card Authorization After Deposit (J21) system control value defines whether the system automatically voids a partially deposited stored value card authorization when the External Payment Service is not in use. See Stored Value Card Deposits for processing details. |
|
Defines whether the service bureau supports authorization reversals for credit card and stored value card payments. Valid values are:
Regardless of the setting of this field, you can still perform stored value card authorization reversals when the card is deactivated; see Stored Value Card Authorization Reversal. |
|
Indicates whether to resubmit failed authorization and deposit requests for credit cards through the External Payment Service. When the request is for authorization and deposit of a failed deposit request: CyberSource: The subsequentAuthReason in the authorization and deposit request is set to 1 if the Supports Auth Resubmission flag is selected; otherwise it is set to 3. Note: If the credit card number changes since the initial deposit request, then the subsequentAuthReason is set to 3, since it is not considered a subsequent authorization and deposit request. External Payment Service: The subsequentAuthReason is set to RESUBMIT; otherwise, if the Supports Auth Resubmission flag is not selected, the subsequentAuthReason is set to REAUTH. Important: Select this flag only if your payment processor supports merchant-initiated resubmission of failed deposits. |
Second Create Authorization Service Screen
Important:
You cannot use this screen to create a new existing authorization service using EFTConnect. Use the Payment Configurations option in Modern View instead.
How to display this screen: Select OK at the First Create Authorization Services Screen.
Field | Description |
---|---|
The method by which the data is transmitted to the service bureau. Valid value is Communication. Optional. |
|
A code that indicates whether transactions are transmitted to/received from the service bureau immediately (online) as each order is entered, or whether groups of transactions are transmitted to/received from the service bureau at predefined times during the day (in batch). Valid values are:
Optional. |
|
Active production system |
This field is ONLY used for PayPal. Indicates whether you are processing in a live environment (production) or in a testing environment. Valid values are:
|
Installment billing? |
Indicates if the service bureau supports installment billing of credit cards. Installment billing plans are typically established for high cost items. Note: This field is informational only and is not used to set up an installment pay plan in Order Administration. Valid values are:
|
Indicates whether a response from the service bureau is received immediately for each authorization transaction. Valid values are:
|
|
Immediate deposit |
Indicates whether the service bureau sends a detailed response to Order Administration. Valid values are:
|
Keep history information? |
Indicates whether transactions sent to the service bureau will be kept online. Typically, this feature is used in test environments. Valid values are:
|
Selected for deposit |
Indicates whether the service bureau is included in the next deposit run. By default, all service bureaus are selected for deposit; however, you can remove a service bureau from the next deposit run at the Select Auth Service for Deposit Screen in Processing Auto Deposits (SDEP). Once you submit the deposit run, the system reselects all service bureaus for the next deposit run. Valid values are:
Display-only. |
Address verification |
Indicates whether you will be using the Address Verification Service provided by the service bureau to verify the customer's address and credit card number. Valid values are:
|
Decline days |
The number of days to hold a declined credit card charge on the system before sending it for an authorization again. This field is not implemented. See Defining Vendor Response Codes for setup information. Numeric, 3 positions; optional. |
Industry format code |
A code that is assigned by the service bureau to identify your company type. Use this field to enter your DBA number. Alphanumeric, 5 positions; optional. |
The primary service bureau that the service bureau uses for its transmission setup. Orders sent to this service bureau are redirected to the primary service bureau defined in this field. If this field is left blank, the data created for this service bureau will be used. Alphanumeric, 3 positions; optional. |
|
Deposit phone # |
The telephone number associated with the deposit service bureau. Informational only. Numeric, 11 positions; optional. |
Authorization phone # |
The telephone number associated with the authorization service bureau. Informational only. Numeric, 11 positions; optional. |
Indicates the method of communication used to transmit transactions between Order Administration and the service bureau. The only valid value is Payment Link, in which the system sends transactions to the service bureau using a point-to-point integration. You must define communication settings in Working with Customer Properties (PROP). The system also uses the Activation and Authorization Reversal integration layer jobs to process stored value card triggers. Optional. |
|
Indicates the multiple to apply to the Response time to determine how long to wait for a response after a connection when you are using an external payment service. For example, if the Response check frequency is 6 and the Response time is 10,000, the system waits 60,000 milliseconds (60 seconds or 1 minute) for a response after connection. Note: If the total response interval is exceeded for an authorization record, the record goes into *RCVD status with a response type of SU, and is then removed from the Credit Card Authorization Transaction table (CCAT00). To avoid potential timeout issues, Oracle recommends that you set the Response Time high enough for the authorization service to prevent issues that could potentially occur if the authorization process times out while processing multiple authorizations for an order. Numeric, 3 positions; optional. |
|
Test mode? |
This field is used for both PayPal and EFTConnect. Indicates whether you are transmitting in test mode. Valid values are:
For PayPal, if selected, the environment key is set to "sandbox" and if unselected, the environment key is set to "live". For EFTConnect, see Payment Configurations. The Environment field can be set to Test or Live. |
Indicates the number of milliseconds to wait for a connection to the service bureau when you are using an external payment service. For example, set this field to 10,000 milliseconds to wait 10 seconds for a connection. Numeric, 5 positions; optional. |
|
Merchant division |
Assigned by the authorization service. Numeric, 5 positions; optional. |
Authorization service provider |
This field is not implemented. Alphanumeric, 10 positions; optional. |
The user name, provided by the service bureau, used to establish a direct connection to the service bureau. Alphanumeric, 64 positions; optional. |
|
The password, provided by the service bureau, used to establish a direct connection to the service bureau. Alphanumeric, 64 positions; optional. |
|
The encrypted signature, provided by the service bureau, used to establish a direct connection to the service bureau. You can also define API credential information at the entity level using the Create Merchant ID by Entity Screen. Alphanumeric, 128 positions; optional. |
|
Note: This field is available only for the CyberSource integration (if the Service Code is set to CYB). Indicates the value to pass as the reconciliationID in a debit deposit, credit deposit, or authorization and deposit request to CyberSource. Available settings are:
For more information see the Order Administration Web Services Guide on My Oracle Support (ID 2953017.1). If the reconciliationID in the request message does not specify an invoice number or alternate order number, then CyberSource assigns a reconciliationID as a reference number for the transaction, and passes it in the response message. If the e-commerce is configured as a reconciliation ID for deposits, the deposit could fail if the e-commerce ID is longer than allowed by the payment processor. See Alternate Order Number Prefix for Order Creation (M76) for more information. Note:
|
Instructions:
-
At the First Create Authorization Services Screen, enter the Service Code, Application, Merchant ID, Charge description and any other information required by the service bureau.
-
Select OK to advance to the Second Create Authorization Service Screen.
-
Continue entering all necessary information to set up the service bureau on your system.
Work with External Authorization Service Screen
Purpose: Information will be provided by Oracle at a later date.
How to display this screen: Select External Service for an authorization service at the Work with Authorization Services Screen. External Authorization Service Access (B25) authority is required.
For more information: See the External Payment Layer RESTful Service reference on My Oracle Support for more information on updating these settings.
Note:
All fields are required, with the exception of the External Service flag.
Field | Description |
---|---|
External Service |
Select this field to have request messages generated for the External Payment Service. |
External URL Prefix |
The prefix that forms the beginning of the URL where messages are sent. Must begin with HTTPS. The message type defines the suffix that is appended to the prefix to create the entire URL. For example, for a credit card authorization request, the entire URL might be https://remote.auth.com:1234/authorization, where remote.auth.com is the remote server, 1234 is the port, and authorization identifies an authorization request. The following endpoints are supported:
Alphanumeric, 600 positions; required if the External Service flag is selected. |
Message Version |
Indicates which message version is supported with version 3.0 being the default version when creating a new authorization service. Previous versions have been removed. Version 3.0 no longer includes tags that pass the credit card number for an order and instead includes tags that pass the card token. It also allows an external merchant application to call for both Credit Cards and Stored Value Cards supported through the External Payment Service and EFTConnect. |
Authentication User |
The user ID for authentication of the messages to the external service. Alphanumeric, 256 positions; required if the External Service flag is selected. |
Authentication Password |
The password for authentication of the messages to the external service. Must be at least 6 positions long, include both numbers and letters, include a special character, and cannot end with a number. Alphanumeric, 256 positions; required if the External Service flag is selected. |