Payment Processing
Payment processing involves payment authorization, settlement, and invoicing. If an order requires payment processing,
the order is not picked up for scheduling or other processing until it is authorized.
Payment Processing can happen in Sterling in two ways i.e. synchronously or asynchronously.
Synchronously – in this transaction and UE can be configured to contact external payment processing system
synchronously and wait for result of authorization or charge request and depending on the success or failure of request,
payment status of order is updated immediately.
Asynchronously - requests for authorization and charge are sent to external PP system in a batch mode and updates can
be made all at once, based on the results of the request.
Payment processing in Sterling Order Management consists of two subprocesses: Authorization and Settlement.
AUTHORIZATION PROCESS - is a process by which the amount to be paid is verified. In case of credit cards, it basically
involves contacting the payment system and blocking the required amount of funds. Payment types may or may not
require this authorization step.
The Payment Collection time-triggered transaction analyzes an order to create authorization requests.
The Payment Execution time-triggered transaction monitors requests created for authorization and provides user exits
to carry out the authorization. The user exit can process the authorization request in any one of the following ways:
•asynchronous processing- batch processing
•synchronous processing to carry out the authorization immediately by interfacing to an external payment processing
system, and pass back the authorized amount.
•Place a request to try again later if the interface to the payment system is not accessibale.
Once authorization is received, the Payment Collection transaction changes the payment status to AUTHORIZED.
SETTLEMENT PROCESS - It involves collecting the funds for the amount recorded for an order. For example, when using
credit cards, the settlement process specifically involves contacting the payment system and collecting the required
amount of funds against the credit card.
Payment Collection analyzes orders to create settlement requests. This is a request for Sterling Order Management to
complete a settlement. If the payment rule applicable for the order requires both authorization and settlement, the
settlement requests are created only against existing authorizations which are not expired.
Payment Execution monitors settlement requests. This time-triggered transaction provides user exits to carry out the
settlement. The user exits can process the settlement request in one of the following ways:
•Request asynchronous processing,. In this, Sterling interacts to the payment system are run in batch mode.
•Carry out the settlement immediately and pass back the settlement amount.
•Place a request to try again later if the interface to the payment system is inoperable.
The Sterling Order Management time-triggered transactions change the payment status of the order to PAID once
payment is received for the complete order amount.
Transactions –
•Payment Execution - Processes all requests that are pending authorization and charging. It reads all open requests for
authorization and charges and invokes the appropriate user exits for executing the request.
•Payment Collection - Analyzes the orders and determines the amount for which an authorization or charge request(s)
should be created.
APIs-
Request Collection
Execute Collection
ProcessOrderPayment - used to invoke the requestCollection() and executeCollection() APIs within a single API.
TABLEs –
YFS_CHARGE_TRANSACTION - stores information about financial transactions associated with order processing. Every
action carried out on an order which may have an impact on financial components is logged in this table.
• OPEN: Indicates that this record is in open status.
• CLOSED: Indicates that this record is in closed status.
• ERROR: Indicates that this record has encountered an error.
• CHECKED: Indicates that this record is in its final status.
• VOIDED: Indicates that this record is in voided status. .
YFS_CHARGE_TRAN_REQUEST – stores the Payment Status of the request.
• AWAIT_AUTH - Part of the order amount is pending authorization.
• REQUESTED_AUTH - The authorization request has been sent, but a reply has not been received from the
payment system. This status only occurs in asynchronous environments.
• AUTHORIZED - The order amount is less than or equal to the authorized amount. When delayed
reauthorization is configured, an AUTHORIZED status indicates that the order can move through the
pipeline, but may not indicate full authorization.
• FAILED_AUTH - An authorization request failed.
