Introducing the PayU Hub

Designed from the ground up for optimizing payment processing. Powered by PaymentsOS.

Collect card details and accept your first payment

Collect card details and accept your first payment

Shake hands with the only heavyweight champion capable of lifting JSON

Allow customers to reuse their card information

Powered by PaymentsOS

PaymentsOS is the technology infrastructure that powers the PayU Hub. Designed to work as a payments operating system of its own accord (hence PaymentsOS), it provides you with a comprehensive toolset for payment processing. This includes:

  • A single entry point for processing payment requests. Using PaymentsOS, you communicate through a single API rather than setting-up communication channels to multiple payment providers.

  • Functionality for dynamically routing a payment request to the most optimal payment provider. Dynamic routing is based on business rules such as fees, acceptance rates, availability and response times.

  • The ability to analyze your payments performance. Using the insights gained, you can then make informed decisions about tweaking your business rules to further reduce abandonment rates and card declines and improve your bottom line.

  • The ability to minimize your PCI compliance scope. PaymentsOS reduces the burden of PCI compliance via secure credit card collection and tokenization.

Integration Overview

Let’s take a birds-eye view of the steps needed to integrate with PaymentsOS. Looking down on the integration landscape, you will notice a total of 4 steps: configure, develop, test and deploy to production.

Test and Live Toggle

Step 1: Configure your environment

Add the providers you will transact against and define the business units that will accept payments. See Setting-up PaymentsOS.

Step 2: Develop client-side and server-side code

Write client-side code for collecting a customer’s card information and server-side code for handling all required transaction flows.

To start collecting card information, understand the options available to you and review the code samples for using our client-side Javascript API or Secure Fields Form. Then get a feel for implementing a one-step (Charge) payment flow by following the procedures in Accepting a Payment.

Once you are familiar with the basics of a client-side and server-side implementation, move on to read about the other payment flows and operations that we support.

Step 3: Test your integration

Verify that your integration works as expected. As a best practice, you should configure, develop and test your integration in a development and staging environment before going live. Review our guidelines for setting up your environments and learn how to use the mock provider for running tests. We also summarized the test cases you should execute before moving to production.

Step 4: Deploy to production

This is the moment when your efforts come to fruition! So, once you’re confident that your setup and integration is production-ready, deploy your code to the production environment and start live transactions.

Payment Flow

At a high level, processing a payment with PaymentsOS involves the following sequence of events:

Test and Live Toggle

What’s next?


Topics in this Section

Quick Start

Flows and Operations

Connect

Services

3DS authentication, risk management and network tokens.

Features

Development Tools

Testing

Security

Reporting

Last modified January 20, 2022