RSB

Follow the standard PaymentsOS integration procedure, and then apply the relevant extra specifications in this section to integrate with RSB.

API Version

Minimum required API version: 1.1.0

Payment Methods

The following table lists all supported payment methods.

Payment Method	Payment Method Type
American Express	Cards
DINERS	Cards
JCB	Cards
MASTERCARD	Cards
MIR	Cards
VISA	Cards

Currencies

RUB

Features

The following table provides an overview of all supported and non-supported features.

Feature	Supported
3DS 2.0 External	No
3DS 2.0 PaymentsOS-handled	No
3DS 2.0 Provider-handled	No
3DS 2.0 Self-handled	No
Installments	No
Level 2 and 3 Data	No
Multi-seller Payments	No
Network Tokens	No
Payment Facilitator	No
PayU Risk	No
Pre-authorization	No
Retrieve Supported Payment Methods	No
Retrieve Supported Plans	No
Statement Soft Descriptor	No
Stored Credentials Flag	No
Transaction Processing without CVV	Yes

Requests

The following table lists all supported requests for card-based transactions. Use the bodybuilder to create a sample request body for each request type.

Request	Partial/Multiple	Mode	Notes
Authorize	Partial and multiple are not supported	Asynchronous or Synchronous	The request is asynchronous (will return a status of `Pending`) in the event of a provider network error. For more information, see Request Retries in the Event of a Provider Network Error.
Capture	Both partial and multiple are supported	Synchronous
Charge	Not Applicable	Asynchronous or Synchronous	The request is asynchronous (will return a status of `Pending`) in the event of a provider network error. For more information, see Request Retries in the Event of a Provider Network Error.
Refund	Both partial and multiple are supported	Asynchronous or Synchronous	The request is asynchronous (will return a status of `Pending`) in the event of a provider network error. For more information, see Request Retries in the Event of a Provider Network Error.
Void	Not Applicable	Synchronous

Request Retries in the Event of a Provider Network Error

Since requests with RSB are not idempotent safe, we cannot deduce the status of a request in the event of a provider_network_error. We will therefore return a 201 status code with a request status of Failed. Beware that creating a new transaction for the same payment may result in a double-charge.

Setup Procedures

The following table lists the setup procedures that are specific to this provider.

Configuration	Required/Optional
In the PaymentsOS Control Center, configure the following credentials: certificate. Copy the certificate string from the .pem file. For help in creating a certificate, review the instructions in the RSB documentation (will download as a PDF file). private-key	Required
In your RSB account, configure COB (Close of Business Day) to ensure funds are automatically settled at the end of each business day. Login to your RSB account and configure your business day closing schedule in user > settings.	Required
In your RSB account, disable CVV if required.Contact RSB support for assistance.	Optional
In your RSB account, enable 3DS. For help, see Enabling 3DS.	Optional
In your RSB account, configure partial/multiple capture. Contact RSB support for assistance.	Optional

Integration Procedures

The following sections list the integration procedures that are specific to this provider.

Enabling 3DS

Note

3DS must be implemented as part of a redirection flow. For an overview of how to implement a redirection flow, see Implementing a Redirection Flow.

If you require 3DS, contact RSB support to configure the following IPN URLs in your RSB environment:

For working with the PaymentsOS test environment: https://api.paymentsos.com/callbacks/rsb/test/callbacks
For working with the PaymentsOS live environment: https://api.paymentsos.com/callbacks/rsb/live/callbacks

After configuring the IPN URLs, configure Webhooks in your PaymentsOS environment to receive updates when a change in a transaction status occurs.

As a last step, make sure to include provider_specific_data with an is3ds value of true in your Create Authorization or Create Charge API requests:

"provider_specific_data": {
	"rsb": {
		"is3ds": "true"
	}
}

Last modified December 7, 2021