Search Results authorize_payment

Overview

AR_PMT_PROCESS_WRAPPER is an Oracle Receivables (AR) PL/SQL package owned by the APPS schema that serves as an integration wrapper between Oracle Receivables receipt processing and the Oracle iPayments (IBY) payment authorization infrastructure. The package encapsulates the parameter marshalling required to invoke the iPayments Authorize API, specifically IBY_Payment_Adapter_pub.OraPmtReq, by translating Receivables receipt attributes into the record structure expected by the payment adapter layer. The header comment identifies the source file as ARIPAYWS.pls, version 115.2, last modified in June 2004, and declares the package with AUTHID CURRENT_USER, meaning that name resolution and privilege checking for unqualified references execute under the calling user's schema context rather than the definer's. The package is classified as an "OTHER" API in ETRM, indicating it is an internal or utility wrapper rather than a formally published public API such as the Receipts APIs, and it is not referenced by any other documented package. Its principal purpose is to facilitate credit card and other electronic payment authorization and capture flows initiated from Oracle Receivables by abstracting the interface to the external payment processor through iPayments.

Key Procedures and Functions

ETRM documents two procedures in this package:

• AUTHORIZE_PAYMENT — Performs the authorization request against the payment processor for a Receivables receipt. This procedure corresponds directly to the user's search term "authorize_payment" and represents the entry point that submits receipt and customer bank account information to the iPayments Authorize API. It consumes the authorize_input_rec record type declared in the package specification, which packages the customer bank branch, merchant reference, customer bank account name, account number, expiration date, payment server order number, receipt amount, receipt number, and currency code required by the adapter. The result of authorization is intended to be persisted back to the receipt's payment server order reference for subsequent settlement.
• CAPTURE_PAYMENT — Performs the corresponding capture or settlement step, finalizing the previously authorized transaction against the payment processor. Capture typically occurs after the authorization has succeeded and the receipt is ready for funds transfer.

The specification also declares two supporting record types: receipt_info_rec, which captures generic receipt context (cash receipt identifier, receipt history identifier, amounts in entered and accounted form, customer bank account, pay-from customer, and site use), and authorize_input_rec, described above. These types allow callers and customizations to pass structured payment data without depending on positional parameter lists.

Tables Accessed

The package operates against the following Oracle Receivables and Oracle Payables base tables through APPS synonyms:

• AR_CASH_RECEIPTS — The primary receipt entity. The wrapper reads receipt amount, receipt number, payment server order number, customer bank account, pay-from customer, and customer site use, all of which feed the authorization request.
• AR_CASH_RECEIPT_HISTORY — Stores receipt state and amount history, including entered and accounted amounts used in the receipt information record.
• AR_RECEIPT_METHODS — Provides the merchant reference associated with the receipt method, identifying the payment processor configuration under which the authorization is submitted.
• AP_BANK_ACCOUNTS — Supplies customer bank account details (bank branch, account name, account number, and inactive date used as the expiration reference) needed by the iPayments adapter.

These tables are read to assemble the authorization payload; the wrapper itself generally does not own the write-back of results, which occurs through the Receipts APIs and iPayments result processing.

Usage Notes

AR_PMT_PROCESS_WRAPPER is an internal integration utility rather than a supported public API. It is most commonly invoked indirectly when a Receivables user processes an electronic receipt through the Receipts window with a receipt method configured for iPayments authorization, or through related concurrent flows that submit receipts for payment processing. Because the package is declared AUTHID CURRENT_USER, any custom code invoking it must run under a schema with appropriate execute privileges and access to the underlying APPS synonyms. Customizations that call AUTHORIZE_PAYMENT or CAPTURE_PAYMENT directly should be treated as unsupported extensions, since the package is shipped with an noship source tag and offers no documented public contract beyond the declared record types and procedures. Oracle's supported integration path for payment authorization and capture remains the Receipts APIs and the iPayments adapter layer, to which this wrapper is subordinate.