Skip to content
Last updated

Process Payments

Overview

This section provides an overview of how to process payments using Ryft once a Payment Session has been created. It covers the necessary steps to set up a payment processing system and handle the results of payment transactions.

The payment processing procedure follows directly after the creation of a Payment Session, which returns a clientSecret value required to finalise the payment

If a Payment Session is not created, the payment cannot be completed. Please refer to the Initiate Payments section for more details on creating a Payment Session.

From this point, the payment can be processed either:

  • an embedded SDK, available for multiple platforms so merchants can integrate using their preferred stack, or
  • an Android or iOS mobile SDKs for native mobile applications, or
  • through a server-to-server approach, provided the merchant is PCI compliant.

The SDK is the recommended approach for most merchants compared to server-to-server integration, as it simplifies the integration process and reduces PCI compliance requirements. It enables merchants to securely handle payment information without directly managing sensitive data.

In practice, the SDK provides a secure way to collect payment details from customers, so that when they click the "Pay" button on your checkout page, you will receive:

  • An immediate response from the SDK indicating whether the transaction was successful;
  • An asyncronous webhook event that you can use to record the transaction in your system.

SDK Languages

We currently provide an SDK for the following environments:

Client-Side Platforms

Server-Side Technologies

Further Reading