In payment processing, it is critical to ensure that payment files sent to payment systems and financial institutions are valid, in addition to being correctly formatted. If this is not done, the payment process is slowed, which results in additional time and cost due to problem resolution. To help achieve straight-through processing, Oracle Payments enables you to ensure that payment-related validations are present.
Oracle Payments provides seeded validations that are associated with the supported payment formats by default. Validations are implemented using a flexible framework that enables you to assign new validation rules. You can choose between using the seeded library of validations, using your newly added validations, or using some combination of these rules.
Some of the system validations are:
Payee bank account must be active.
Checks whether the payment is resulting in international payment. If it is an international payment, then checks whether the "Allow international Payment" is selected at the Payee bank account level.
Checks whether the payment currency is same as the payee bank account currency. If it is not, then checks if it supports multi currency.
The default validation rules are business rules that are followed in the business. If you look at the validation rules mentioned, most of them are general standard practices followed in the business. There is no specific document on the default validations and we cannot document all the general business rules also.
Additionally, you have choices with respect to the timing of validation rule execution. Validations can be assigned toward the beginning or toward the end of the payment process. A combination of rule assignments can also be used. You can adapt validation rule assignment to support your business model. For example, assigning and executing validations toward the beginning of the payment process may be best for a decentralized payment environment, whereas assigning and executing validations toward the end of the payment process may be better in a shared service environment, where payment specialists can resolve validation failures.
Seeded validations can be assigned in one the following places:
Create Payment Method page--funds capture side
Create Payment Method page--funds disbursement side
Create/Update Format page
Validations are comprised of the following categories:
Pre-defined Validations
User-defined Validations
A country-specific validation is a validation related to a specific country. It is comprised of a code and multiple sub-validations that are required for the specific country, a validation point, and additional specifications regarding the payment formats and/or payment methods to which the validations are applicable. Country-specific validations are seeded by Oracle Payments and cannot be modified. For a listing of Oracle Payments seeded, country-specific validations, see Country-Specific Validations.
The table below describes the elements of a country-specific validation.
Elements of a Country-Specific Validation
User-defined validations are basic validations that correspond to simple operations. For example, validating that the length of a certain field does not exceed a specific character limit is an example of a user-defined validation. These validations can be used as components, or building blocks, to build more complex validations. They enable you to validate, for example, the following conditions:
length of a field
whether a field is populated
whether a field contains non-numerical characters
To illustrate the application of user-defined validations, you can create a new payment format, for example, in the Create Format setup page and then assign validations to the newly created format.
Note: The user-defined validations are executed at the same points as the country-specific validations. For information on validation points, see the Validation Point, in the Elements of a Country-Specific Validation table.