Sberbank

Sberbank has some special integration requirements. Follow the standard PaymentsOS integration procedure, and then apply the relevant extra specifications described below.

Specifications for Card-based Transactions

The following table lists the integration specifications for Sberbank.

SpecificationsDetails
Minimum PaymentsOS API Version1.1.0
Requests
  • Authorize
  • Capture (including partial)
  • Charge
  • Refund (including multiple/partial)
  • Void
Limitations:
Void is only supported after Authorize.
CurrenciesRUB
Payment Methods
  • MASTERCARD
  • MIR
  • VISA
Transaction Processing without CVVSupported
3DS RedirectionNot supported

Configurations

The following table lists the configurations that are specific to Sberbank.

ConfigurationRequired/Optional
In the PaymentsOS Control Center, configure the following credentials:
  • userName: The user name supplied by Sberbank
  • password: The password name supplied by Sberbank
Required
In your Sberbank account, set 3DSecure to disable. This is required since PaymentsOS does not yet support 3DSecure authentication for Sberbank.Required
In your Sberbank account, set SSL payment to enable. This is required since PaymentsOS does not yet support 3DSecure authentication for Sberbank (3DSecure authentication is needed if you disable SSL payment).Required
In your Sberbank account, set Payment from merchant side to enable. This is required for implementing payments via an API.Required
In your Sberbank account, set Number of payment attempts to 1 to prevent duplicate charges.Required
In your Sberbank account, set Payment without CVC to enable if you want to allow post authorization and post charge requests to be processed without a cvv number.Optional
In your Sberbank account, set 2-phase payment to enable if you want to implement a 2-step payment flow. For more information about payment flows, see Flows and Operations.Optional
In your Sberbank account, set the payment expiration time if you want to apply this setting at the account level. This is the time period in seconds within which you can perform a capture after a successful authorization request. The default is 20 minutes. Format: Only digits, maximum 9 digits.
Note: The payment expiration time can also be passed at the transaction level, in the provider_specific_data object.
Optional

Sample Requests

Use the bodybuilder to create a sample request body for each request type.

Testing

You can use the following Sberbank test cards for testing:

Card number Expiration date CVV Notes
4111 1111 1111 1111 2019/12 123 Success
5555 5555 5555 5599 2019/12 123 Success
5555 5555 5555 5557 2019/12 123 Failure
4000 0000 0000 0002 2019/12 123 Failure
4444 3333 2222 1111 2019/12 123 Failure
5555 5555 4444 4442 2019/12 123 Failure
4444 4444 4444 4422 2019/12 123 Failure
4444 4444 1111 1111 2019/12 123 Failure
4444 4444 4444 6666 2019/12 123 Failure
4444 4444 4444 4455 2019/12 123 Failure
4444 4444 9999 9999 2019/12 123 Failure
4444 4444 4444 3333 2019/12 123 Failure
4408 8962 5320 5448 2019/12 123 Failure
4012 8888 8888 1881 2019/12 123 Failure
4563 9601 2200 1999 2019/12 123 Failure

results matching ""

    No results matching ""