eBucks (Enterprise API)

This page serves as a supplementary guide for integrating eBucks into the payment flow and is to be read in conjunction with the PayU Enterprise API integration documentation.

The PayU Enterprise API provides merchants a seamless integration into the PayU service to process transaction requests using their own UI. All request calls for the Enterprise API are done via service side calls to PayU with SOAP web services.

API call sequence

The following sets out the golden path integration for eBucks via the Enterprise API

API call sequence - Payments

Golden Thread:

Although no PARTNERAPI request requires a "payUReference", it is recommended to supply one if one has been returned on any previous request made to PayU. This will provide/create a "Golden Thread" in the transaction history to help the support team with problem solving.

Any PARTNERAPI request that does not receive a "payUReference", will generate a new one and return it in the the response. This reference can then be used in any subsequent call in the transaction chain.

Note: No transaction record will be create for a non transactional request (e.g. PARTNERAPI), it will only be created for transactional requests like DoTransaction & SetTransaction. If a unique "payUReference" is supplied on a transactional request, the transaction record will be created with the supplied reference.

The following calls are required to accomplish a payment via Enterprise API to eBucks

ebucks is currently only available as a 'PAYMENT' transaction type on the Enterprise API

API call sequence - Supplementary

The following is not necessary to complete an successful eBucks transaction but can be used to as supplementary calls to facilitate various eBucks functionality