General Introduction

Payment Gateway overview

“SBC Payment Gateway” (here and hereafter System, Payment Gateway or SBC) is a PCI DSS certified platform, which provides accepting, processing, storage and transmitting of payment data between participants of payment processes.

Main participants:

Payers or Receivers

end customers of merchants.

Connecting Party

merchants themselves, PSP/Payment institutions which represent merchants, or third-party systems for data exchange (CRM, BI, monitoring).

Processors

integrated external payment institutions and payment providers.
Payment Gateway provides the following methods of accepting payment data:

  1. API available on the Internet

  2. POS-terminals

  3. Virtual terminal for manual entry of payment data, received by e-mail and phone

Payment Gateway provides access to user accounts. It has the following user roles. Each root entity, can have its own Employees who can get access to the data from the root entity, but with certain restrictions:

Merchant

provided to the merchant’s representatives (Connecting Party).

Reseller

provided to the agent, which engage merchants for Payment Gateway.

Manager

provided to the representatives of Payment Gateway.

Note

See all terms definitions in Glossary.

Connecting Party integration scenario

Depending on the PCI compliance and business requirements, Connecting party integrates to Payment Gateway via Server-to-Server APIs, Hosted payment form APIs or a combination of them. Each integration option is provided in API Use-Cases section, and each API Use-Case provides clear instructions which API commands to call on each stage of the payment flow and how to handle their results. All APIs are asynchronous. Common utilities section provides added value services which might be enabled by request. FAQ page helps to resolve common issues during Connecting Party integration.

SBC support manager configures Projects with connected Endpoints and Endpoint Groups (if needed) for one or multiple merchant accounts of Connecting Party in Payment Gateway. For API integration, Connecting party receives the following data from SBC. This data can be provided independently for sandbox (test) and production environment. Any additional required credentials are mentioned in relevant API Use-Cases.

Main required credentials are:

  1. Endpoint IDs per currency or Endpoint Group IDs for multicurrency integration (see reference schema below).

  2. Merchant login.

  3. Merchant control key.

  4. Integration scenario documentation.

title Options for multi-currency processing integration package "Integration to Endpoint Group" { class "layoutHelper1" #ffe6cc;line:black;line.dotted class "Project\n currency A" #dae8fc;line:black;line.dotted class "Project\n currency B" #dae8fc;line:black;line.dotted class "Endpoint\n currency A" #ffe6cc;line:black;line.dotted class "Endpoint\n currency B" #ffe6cc;line:black;line.dotted class "Endpoint\nGroup" #ffe6cc;line:black;line.dotted } package "Integration to multiple Endpoints" { class "layoutHelper2\n" #ffe6cc;line:black;line.dotted class "Project\n currency C" #dae8fc;line:black;line.dotted class "Project\n currency D" #dae8fc;line:black;line.dotted class "Endpoint\n currency C" #ffe6cc;line:black;line.dotted class "Endpoint\n currency D" #ffe6cc;line:black;line.dotted } class "layoutHelper3" #ffe6cc;line:black;line.dotted class "Connecting Party\n (Merchant)" #e1d5e7;line:black;line.dotted "Connecting Party\n (Merchant)" -left-> "Endpoint\nGroup" "Connecting Party\n (Merchant)" -down-> "layoutHelper3" "Connecting Party\n (Merchant)" -down-> "Endpoint\n currency C" "Connecting Party\n (Merchant)" -down-> "Endpoint\n currency D" "Endpoint\nGroup" -down- "Endpoint\n currency A" "Endpoint\nGroup" -down- "Endpoint\n currency B" "Endpoint\n currency C" -down- "Project\n currency C" "Endpoint\n currency D" -down- "Project\n currency D" "Endpoint\n currency A" -down- "Project\n currency A" "Endpoint\n currency B" -down- "Project\n currency B" "Connecting Party\n (Merchant)" -left[hidden]- "layoutHelper1" "Connecting Party\n (Merchant)" -right[hidden]- "layoutHelper2\n" "layoutHelper1" -[hidden]- "Endpoint\n currency A" "layoutHelper1" -[hidden]- "Endpoint\n currency B" "layoutHelper2\n" -[hidden]- "Endpoint\n currency C" "layoutHelper2\n" -[hidden]- "Endpoint\n currency D" hide members hide circle hide layoutHelper1 hide layoutHelper2\n hide layoutHelper3

Connecting Party integration example

  1. Sale Form - integrate hosted payment form processing of E-commerce sale transactions.

  2. Return transactions - integrate processing of refunds.

  3. Connecting Party callbacks - receive transaction data to CRM, BI and other systems.

  4. Forms customization - brand hosted payment forms and provide them to SBC support manager for installation.

  5. Test the solution on sandbox with SBC test scenarios.

  6. Inform SBC support manager about successful finish of testing and request production credentials to start processing payments.