iStore R12 – Statement Billing Address for Credit Cards
This is a cool feature that has been implemented in iStore R12. This involves the implementation of Oracle Payments (previously known as Oracle iPayment). Oracle Payments offers the merchants ability to turn on or off the option to enforce iStore users to provide the Statement Billing Address. This has been done, mainly, to prevent fraudulent transactions. This is used in conjunction with the AVS Code verification that is an in-built functionality in Oracle Payments (and earlier, iPayment), where the Credit Card companies return a couple of Status Flags, based on the Street and Zip Code match. Based on the values of the Status Flags (‘Y’ for Yes its a match, ‘N’ for No its not a match), the Order in Order Management or in iStore can be placed on Hold. The Order however does get booked, but it needs manual intervention to release the order to be shipped.
When implementers mark a credit card statement address as mandatory in Oracle Payments, Oracle iStore also marks this as mandatoryinformation customers must select as part of credit card data in the following areas:
• Payment Book
• Express Checkout Preferences
• Payment and Billing Information Page during checkout
If credit card statement address is not mandatory in Oracle Payments, Oracle iStore does not expose credit card billing statement address anywhere in the Customer Application.
Note: This functionality applies only to newly created credit card data, or to updated credit card data. Data from previously entered credit cards will not be affected, unless the customer attempts to update an existing credit card; in this case, if the billing statement address is mandatory, during update the customer will be required to select the statement address.