Skip Headers

Oracle Payments User's Guide
Release 12.1
Part Number E13415-04
Go to Table of Contents
Contents
Go to previous page
Previous
Go to next page
Next

Funds Capture Process Home Pages

Introduction

The Funds Capture Process Home page and its associated pages enable the Payment Administrator to monitor the funds capture process. The Funds Capture Process Home page is a read-only page that displays the current status of settlement batches and other settlement transactions that are in-process or recently completed. This page contains links to detailed views of these entities, as well as links that enable the Payment Administrator to retry transactions that have failed due to a temporary circumstantial or system error, such as a communication failure. When the appropriate function security is enabled, typically during the implementation and testing phases, the Funds Capture Process Home page enables the Payment Administrator to access the Transaction Testing pages.

In summary, the Funds Capture Process Home Page and its subsidiary pages enable the Payment Administrator to:

Funds Capture Process Home Page

The Funds Capture Process Home page is the first page the funds capture Payment Administrator sees upon logging in. He uses the page to:

Monitoring Recent Successful Settlement Batches

The Recent Successful Settlement Batches region enables the Payment Administrator to monitor successful settlement batches and to initiate the retrieval of clearing or acknowledgement information. It displays a table containing settlement batches that have reached a successful status (Succeeded or Submitted) in the last 24 hours. Each row in the table displays basic information, plus the status of the batch and a Fetch Clearing icon for Submitted batches that, if clicked on, submits the Fetch Settlement Batch Clearing concurrent program with all the parameters populated with the values of this settlement batch.

Monitoring Recent Failed Operations

The Recent Failed Operations region enables the Payment Administrator to monitor failed operations, both individual transactions and settlement batches, and to initiate the retry action if the Payment Administrator has the necessary security functions enabled.

The table contains transactions and settlement batches that have reached a retryable failure status in the last 24 hours. Each row in the table displays basic information, plus the status of the operation and a Retry icon that, if clicked on, sends the Payment Administrator to the appropriate Retry Warning page before retrying the operation.

Creating and Submitting Settlement Batches

The Create and Submit Settlement Batches content container, displayed on the top right side of the Funds Capture Process Home page, allows the Payment Administrator to initiate creation and submission of settlement batches. The Payment Administrator selects a payment instrument type if he wants to restrict the batches by that parameter. When he clicks the Submit button, Oracle Payments submits the Create Settlement Batches concurrent program with the payment instrument parameter, if selected.

Counting Errors

The Error Count graph counts failures at whatever level they occur, whether individual transactions or settlement batch. The graph shows an absolute number of failed operations, but does not indicate them within the context of the total volume of operations processed.

Searching for Settlements Batches, Settlements, Authorizations, or Credits

The Search subregion of the side navigation bar enables the Payment Administrator to quickly search for an operation by choosing the operation type from the drop-down list and entering that operation’s payment system order number (or settlement batch reference, if searching for a settlement batch) in the field to the left of the Go button.

Submitting Funds Capture Concurrent Programs

The Shortcuts subregion of the side navigation bar enables the Payment Administrator to quickly invoke the following funds capture programs as concurrent requests:

Each program link in this subregion enables the Payment Administrator to specify applicable parameters, if any, schedule the concurrent request, and specify who should receive notification of the request.

The Perform All (Funds Capture) Actions concurrent request, with no parameters, runs the following concurrent programs:

Submitting and Monitoring Funds Capture Concurrent Requests

The Concurrent Requests subregion of the side navigation bar enables the Payment Administrator to quickly submit and monitor any concurrent requests. Like the links in the Shortcuts subregion, these links enable the Payment Administrator to specify applicable parameters, schedule the concurrent request, specify who should receive notification of the request, and then monitor the submission.

The table below describes the funds capture concurrent programs provided by Oracle Payments.

Funds Capture Concurrent Programs
Funds Capture Concurrent Programs Description
Create Settlement Batches Groups settlements into batches and submits them to payment systems.
Fetch Settlement Batch Clearing After a batch has been submitted to a payment system, this program fetches the results, if any.
Perform all Funds Capture Actions Runs the following funds capture programs:
  • Create Settlement Batches

  • Fetch Settlement Batch Clearing

  • Retry Settlement Batches

  • Submit Offline Transactions

Retry Settlement Batches Attempts to resubmit a pending settlement batch.
Send Receipt of Payment Notifications Creates payment notifications that are sent to payers to inform them that payments have been made.
Settlement Batch Accompanying Letter Creates an accompanying letter for a settlement batch.
Submit Offline Transactions Submits offline transactions to a gateway model payment system.

Searching and Viewing Settlement Batch Information

Any time after a settlement batch is created, the Payment Administrator can view complete information about it. The Settlement Batch pages are comprised of the Settlement Batch Search page, as well as a Settlement Batch Details page. The Payment Administrator can search for a settlement batch and then drill down to the settlement batch details. From there, he can drill down to the individual transaction details page. The Settlement Batch Details page can also be reached through the Funds Capture Process Home page. The Settlement Batch Details page is display-only and displays nearly all settlement batch information.

Results Table Columns

If the Status column in the results table shows a status of Communication Error or System Failure, and the appropriate function security is enabled, then the Retry icon is displayed. The Retry icon links to the Settlement Batch Retry Warning page.

Searching and Viewing Authorization Information

At any time, the Payment Administrator can view complete information about an authorization. This includes credit card authorizations, credit card authorization and settlements, debit card authorizations, whether or not settlement is done as part of the authorization, and bank account validations.

The Authorization pages are comprised of the Authorization Search page and an Authorization Details page. The Payment Administrator can search for an authorization and then drill down to the details page. The Authorization Details page can also be reached through links on the Funds Capture Process Home page. Detail pages for offline authorizations that are sent in settlement batches can also be reached through the Settlement Batch Details page. The Settlement Batch Details page is read-only and displays nearly all authorization information.

Results Table Columns

If the Status column in the results table shows a status of Communication Error or System Failure, and the appropriate function security is enabled, then the Retry icon is displayed. The Retry icon links to the Authorization Retry Warning page.

Searching and Viewing Settlement Information

At any time, the Payment Administrator can view complete information about a settlement. This includes credit card settlements, debit card settlements, and bank account transfers.

The Settlement pages are comprised of the Settlement Search page and a Settlement Details page. The Payment Administrator can search for a settlement and then drill down to the details page. The Settlement Details page can also be reached through links on the Funds Capture Process Home page or the Settlement Batch Details page. The Settlement Details page is read-only and displays nearly all settlement information.

Results Table Columns

If the Status column in the results table shows a status of Communication Error or System Failure, and the appropriate function security is enabled, then the Retry icon is displayed. The Retry icon links to the Settlement Retry Warning page.

Searching and Viewing Credit Information

At any time, the Payment Administrator can view complete information about one or more credits. This includes both credit card refunds, which are reversals of earlier settlements, stand-alone credits, and bank account transfer credits.

The Credit pages are comprised of the Credit Search page and a Credit Details page. The Payment Administrator can search for a credit and then drill down to the details page. The Credit Details page can also be reached through links on the Funds Capture Process Home page or the Settlement Batch Details page. The Credit Details page is read-only and displays nearly all credit information.

Results Table Columns

If the Status column in the results table shows a status of Communication Error or System Failure, and the appropriate function security is enabled, then the Retry icon is displayed. The Retry icon links to the Credit Retry Warning page.

Retrying Transactions

A Payment Administrator may retry operations that have failed, such as authorizations, settlements, credits, or settlement batch creation due to communication or general processing errors if he has the appropriate security enabled.

Retrying operations can be problematic, however. The source product that initiated a transaction request may not have a way to know when a failed transaction has been retried and the result of the retry. In addition, the source product may initiate a new transaction to replace the old failed one. Since source products are responsible for larger tasks like order management and accounting, such a disconnect could lead to incorrect source product behavior, incorrect accounting, and charging or refunding more than necessary.

Retrying operations, especially credits, without oversight from source products can also provide opportunities for fraud or theft. Retries, therefore, are subjected to function security, and when enabled and performed, are accompanied by warning messages to keep you from assuming that the source product knows the results of a retry.

Creating Settlement Batches

The Create Settlement Batches concurrent program is used to settle batches and submit them to the appropriate payment systems.

Note: In some cases, Oracle Payments may be set up to place batches into a file system instead of transmitting them. This program supports this approach also.

This concurrent program finds pending authorization, settlement, and credit transactions intended for processor-model payment systems. It then groups these transactions into settlement batches and submits them to the payment system using the appropriate transmission and security configurations.

Retrying Settlement Batches

This program takes a single settlement batch and attempts to resubmit it to the appropriate payment system.

Fetching Settlement Batch Clearing

The Fetch Settlement Batch Clearing concurrent program is used to retrieve batch acknowledgement or clearing information from the payment system and updates batch headers and transactions in Oracle Payments.

Note: In some cases, the payment system pushes clearing information to the deploying company’s file system. When this occurs, the concurrent program simply retrieves the data from the local file system.

This concurrent program attempts to obtain all requested clearing information from payment systems and incorporates the information by parsing it and updates the relevant transaction and batch tables. Based on the payment system’s behavior, this may mean downloading and parsing a file from the payment system server, parsing a file that has already been pushed to the deploying company by the payment system, or doing nothing for payment systems that do not provide electronic clearing information.

Note: The Fetch Settlement Batch program can handle clearing information for transactions with different payment instrument types in the same clearing file.

Submitting Offline Transactions

The Submit Offline Transactions concurrent program is used to submit offline non-batch transactions to the intended gateway payment system.

Note: Offline transactions are typically batched for processor model payment systems, but not for gateways.

This concurrent program finds pending offline transactions with a settlement date that is equal to or less than the current date and submits them to their intended payment gateway.

To submit offline transactions, navigate to the Funds Capture Process Home page and click the Submit Offline Operations link under the Shortcuts subregion.