Search Results process_credit_card

Overview

IBE_PAYMENT_INT_PVT is a private PL/SQL package body in the APPS schema that supports payment instrument handling within the Oracle iStore (IBE) module, specifically for credit card checkout and one-click ordering flows. Its header comment identifies the intended package name as IBE_Quote_Checkout_Pvt, reflecting its origin in the quote-to-checkout integration path. The package encapsulates the internal logic required to persist credit card details, validate payment channel configurations, and migrate legacy payment instrument data into the Oracle Payments (IBY) data model.

The package is classified as PVT, meaning it is not intended for direct invocation by external callers. It relies on the public APIs in IBY_FNDCPT_SETUP_PUB and IBY_FNDCPT_COMMON_PUB to create and manage payment instruments and their assignments, and on HZ_LOCATION_V2PUB and related objects to resolve party site and location information. The presence of the last-updated header stamp (IBEVPINB.pls 120.16, 2005/12/15) indicates the file predates the 12.1.1 and 12.2.2 releases and has been carried forward largely unchanged, which is typical for iStore checkout infrastructure.

Key Procedures and Functions

• SAVE_CREDIT_CARD — The central routine. It accepts credit card identification, assignment, currency, card number, holder name, expiration date, card type, party and customer identifiers, and a statement address, and returns the resulting credit card and assignment identifiers along with standard FND_API return status and message outputs. It orchestrates calls into IBY_FNDCPT_SETUP_PUB using credit card, payment instrument, and payment instrument assignment record types, and resolves location data via HZ_LOCATION_V2PUB.
• CHECK_PAYMENT_CHANNEL_SETUPS — Validates that the payment channel and related setup configuration exist and are usable before checkout commits payment data.
• PRINT_DEBUG_LOG — Writes diagnostic output when debug mode (IBE_UTIL.G_DEBUGON) is enabled, used to trace execution paths during troubleshooting.
• MIG_EXP_CHECKOUT_PAY_SETUP — Supports migration of existing checkout payment setup data, aligning legacy configuration with the current Oracle Payments structures.
• MIGRATE_PRIMARY_CC — Migrates primary credit card designations, preserving which instrument a customer or party treats as default.
• MIGRATE_IBE_CC_DATA — Performs the bulk migration of iStore credit card records into the IBY instrument model, typically as part of an upgrade or one-time data conversion effort.

Tables Accessed

• IBY_PMT_INSTR_USES_ALL — The primary target for payment instrument usage records, storing how an instrument is used and its assignment context. This is the table most directly associated with the user's search term.
• IBY_EXTERNAL_PAYERS_ALL / _S — Stores external payer definitions linking parties to payment instruments.
• IBY_UPG_INSTRUMENTS — Staging area for instrument records during upgrade and migration processing.
• HZ_PARTY_SITES — Resolves party site information for statement addresses and payer context.
• IBE_ORD_ONECLICK, IBE_ORD_ONECLICK_ALL — One-click ordering configuration that drives stored payment preferences.
• FND_USER, FND_USER_PREFERENCES — User identity and preference lookup used when associating instruments with the acting user.
• DUAL — Used for single-row functional calls and sequence or date retrieval.

Usage Notes

Because this is a PVT package, invocation occurs indirectly. iStore checkout pages and one-click ordering logic call these routines through higher-level public APIs during checkout completion, when a shopper elects to store a credit card for future use. The migration procedures are typically driven by upgrade or data conversion scripts executed during an Oracle Payments or iStore implementation, and may be launched from concurrent program wrappers or SQL*Plus during cutover. The package is referenced by two other packages in the ETRM inventory, confirming it sits beneath a thin public layer. Customizations should avoid calling IBE_PAYMENT_INT_PVT directly, since its signature and internal calls to IBY_FNDCPT_SETUP_PUB record types are subject to change without public API guarantees.