Pair Incoming Payment
This chapter dives into the pairing process of incoming payments with the registered documents in OCS.io. This mechanism involves correlating any attribute from the incoming payment with any attribute present on the pre-registered documents.
Primarily, the working procedure is subdivided into two major parts - Promise to Pay, and Non-Promise to Pay. Please be noted that the condition of how to categorize a payment into either of the sections is a customizable feature which may vary from deployment to deployment.
Promise to Pay
In the section of Promise to Pay, the system initially reviews if the incoming payment is characterized as a promise to pay. This settlement is ruled by a condition which can be tailored based on any characteristic of the specific deployment such as file name, an exclusive attribute in the payment, or any other critical factor. Upon the incoming payment satisfying the required condition, it is considered as a pledge to pay, and the system advances with the pairing process.
The pairing protocol entails linking any characteristic from the incoming payment to a similar attribute in the pledged payment. These matching attributes are again deployment-specific and can be customized as per requirements.
Non-Promise to Pay
In the Non-Promise to Pay section, the payment goes through an identification process if it does not satisfy the condition to be termed as a promise to pay. The system checks for various combinations of payment attributes and document attributes to establish a match. Please note that these combinations can be altered to meet specific deployment requirements.
Unidentified Payments
If the incoming payment does not correspond to any created document or pledged payment, it is classified as an unidentified payment, and the procedure terminates.
Registering Payments
Post the pairing process; the payment is registered, and in the absence of any discrepancies, the result is set to OK.