PPS ORIAN API

Overview

The PrePay Solutions ORIAN (Open Real-time Integrated Authorisations and Notifications) feature allows customers integrated with the PPS processing platform to more closely monitor and control programme activity.

Note that today ORIAN has support for transaction activity only.

ORIAN provides the following high level capabilities:

Each of these capabilities may be switched on at the level of a PPS Product Class. Further configurable options are also defined for each high level capability.

Delegated Authorisation

The Delegated Authorisation capability allows a party external to PPS (termed the External Authorisation Entity) to make authorisation decisions in real time. To start using the Delegated Authorisation capability the following settings must be agreed with and configured by PPS for a candidate Product Class.

Note that making use of the Delegated Authorisation capability does not mean that PPS business rules can not also be used. Any configured PPS business rules will be evaluated first and the External Authorisation Entity will only be contacted if all rules are satisfied. All information required for the final decision is forwarded, including the PPS balance, and authorisation is suspended until the decision is received and then returned to the acquiring entity.

Transaction Notifications

The Transaction Notification capability supports the real-time reporting of transaction activity. Transaction Notifications are independent of the authorisation decision provided by the Delegated Authorisation capability but may be used by an External Authorisation Endpoint to aid in management of a remote balance. PPS provide the following notification subscriptions to tailor the notifications received:

Transaction Notifications will be delivered immediately after the transaction has been processed. While notifications are delivered asynchronously to the transaction process it is expected that delivery is as close to real-time as possible.

All notification types provide guaranteed delivery. As such any failure to deliver to the endpoint (after a number of retry attempts) will be identified by PPS Technical Support staff and the transaction resent when the issue has been resolved.

Authorisation Notifications

Authorisation Notifications will be generated by PPS in response to the following authorisation activity (and independent of any Delegated Authorisation activity):

• Approved authorisation requests on schemes with a separate clearing phase
• Authorisation advices on schemes with a separate clearing phase
• Authorisation expiry

Authorisation Notifications do not represent an actual financial transaction but rather an authorisation decision and optionally a reservation of funds pending a separate clearing process.

Decline Notifications

Decline Notifications will be generated by PPS in response to an authorisation decline decision. A decline may be initiated by PPS in the application of security or business rules or by an External Authorisation Entity in the case of Delegated Authorisation. A declined transaction will never impact the available to spend or cleared balance of the account.

Financial Transaction Notifications

A Financial Notification will be generated by PPS in response to a movement of funds (and independent of any Delegated Authorisation activity). The following activity will generate a Financial Notification:

• Approved authorisation requests on schemes without a separate clearing phase (auto-clearing)
• Non-Financial transactions (e.g. PIN change, balance enquiry) with a financial impact (i.e. where a fee is charged).
• Clearing (where a separate clearing phase exists)
• Transactions generated internally by PPS (e.g. account fees, breakage)

These notifications will be delivered at the end of the transaction lifecycle. Transactions notified under this setting will be 'complete' and will not subsequently be altered.

Non-Financial Transaction Notifications

A Non-Financial Transaction Notification will be generated by PPS in response to transaction activity that has no impact on the "available to spend" of the account. The following activity will generate a Non-Financial Notification:

• Balance Enquiries
• PIN Change
• PIN Unblock
• Card Block
• Account Block
• Card Activation

Many non-financial activities also support a reversal/cancel operation that will also generate a notification. Note that if any of these activities have a financial value (e.g. a fee is charged) then they will be published under the Financial rather than Non-Financial category. Also note, Balance enquiries or PIN changes triggered by web service calls, e.g. Transaction History web service or Borneo transaction methods, do not currently generate notifications. Notifications are only generated for ATM balance enquiry or PIN changes.

Direct Debit Mandate Notifications

Direct Debit Mandate Notifications will be generated in response to any creation / change to a direct debit mandate. Notifications will be delivered immediately after the direct debit mandate has been processed. While notifications are delivered asynchronously to the direct debit mandate process it is expected that delivery is as close to real-time as possible.

Screening Notifications

Note: this is an upcoming feature, not currently part of the live version of ORIAN
Screening Notifications will be generated by PPS in response to a change of Screening status in cases where the positive Screening decision was not sent to the customer via Identity Management as part of the initial request.

All notification types provide guaranteed delivery. As such any failure to deliver to the endpoint (after a number of retry attempts) will be identified by PPS Technical Support staff and the direct debit mandate resent when the issue has been resolved.