Skip to content
Menu

Sklep

Ta strona zawiera wszystkie szczegóły potrzebne do zarządzania sklepem za pośrednictwem API. Możesz utworzyć, zaktualizować lub anulować swój sklep, a także dodawać lub usuwać metody płatności.

Utwórz sklep

Aby utworzyć nowy zasób establishment, należy zapoznać się z listą dostępnych punktów końcowych środowiska podaną poniżej:

EnvironmentURLOperation Method & EndpointOperation Description
PRODapi.sibsgateway.comPOST /sibs/onboarding/v1/sponsored-merchant/{merchant-id}/shopCreate a new merchant establishment resource
CERstargate-cer.qly.site1.sibs.ptPOST /sibs/onboarding/v1/sponsored-merchant/{merchant-id}/shopCreate a new merchant establishment resource
Sandboxsandbox.sibsgateway.comPOST /sibs/onboarding/v1/sponsored-merchant/{merchant-id}/shopCreate a new merchant establishment resource

Należy wykonać żądanie POST zawierające następujące parametry nagłówka i ścieżki:

Parameters
ParameterTypeConditionRequiredDescription
Typ zawartościStringObowiązkowyNagłowekapplication/json
X-Request-IDStringObowiązkowyNagłowekID of the request, unique to the call, as determined by the initiating party
merchant-idStringObowiązkowyŚcieżkaID of Sponsored Merchant
x-ibm-client-idStringObowiązkowyNagłowekToken that identifies a client organization. It is provided during onboarding process and must be used in every call

Należy wykonać żądanie POST z następującymi parametrami.

Parametry żądania
Data ElementType LengthConditionDescription
ShopObowiązkowyObject that defines the Merchant Establishment
nameString <=40OpcjonalnyNazwa establishmentu. Gdy to pole jest puste, uwzględniane będą wartości sparametryzowane na poziomie sprzedawcy.
addressStringOpcjonalnyEstablishment Address When these fields are empty, the value to be considered will be the ones parametrized at the Merchant level.
streetString <=100OpcjonalnyUlica
postalcodeString <=25OpcjonalnyKod pocztowy
localityString <=20OpcjonalnyMiejscowość
countryNumber 3-3 Format ISO 3166, Number 3 code (ex: Poland – 616)OpcjonalnyKraj
emailString <=55OpcjonalnyEstablishment Email When these fields are empty, the value to be considered will be the ones parametrized at the Merchant level.
phoneNumberString <=16OpcjonalnyEstablishment Phone When these fields are empty, the value to be considered will be the ones parametrized at the Merchant level.
typeString “Banks” “Wholesale“ “Supermarket“ “Retail“ “Gas Stations“ “Restaurants“ “Hotels“ “Others” “Virtual Establishment“ “Foreign“ “Service Provider“ “Service Entity“ “EMV Tolls“ObowiązkowyEstablishment Type
mccString 4-4ObowiązkowyEstablishment MCC
pkdString 7ObowiązkowyEstablishment CAE
InvoiceIndicatorstring “Payment Facilitator” “Sponsored Merchant” Default: “Payment Facilitator”ObowiązkowyEstablishment Invoice Indicator
productsStringObowiązkowyObject that defines the Establishment Products
productIdString “XPAY-APPL-0-0”, “XPAY-GGLE-0-0”, “PYWK-BNPL-1-0”, “PYWK-BNPL-2-0”, “INTP-BLIK-0-0”, “INTP-BLIK-1-0”, “BLMD-PYBL-0-0”, “KEVN-PYBL-0-0”, “MCC-1-C”, “MCC-1-D”, “MCC-1-P”, “MCC-2-C”, “MCC-2-P”, “MCC-4-C”, “MCC-4-D”, “MCC-4-P”, “MSI-1-D”, “MSI-1-P”, “MSI-2-D”, “MSI-2-P”, “VIS-01-C”, “VIS-01-D”, “VIS-01-P”, “VIS-02-C”, “VIS-02-D”, “VIS-02-P”, “VPY-03-D”, “VPY-03-P”, “VSL-01-C”, “VSL-01-D”, “VSL-01-P”ObowiązkowyMetody płatności wybrane przez klienta. Product ID’s to activate: “INTP-BLIK-0-0” InterPay-BLIK-Domestic “INTP-BLIK-1-0” – InterPay-BLIK-OneClick “BLMD-PYBL-0-0” BlueMedia-PayByLink-Domestic “KEVN-PYBL-0-0” – PayByLink-Kevin “MCC-1-C” – Mastercard-Mastercard-Consumer-Credit “MCC-1-D” – Mastercard-Mastercard-Consumer-Debit “MCC-1-P” – Mastercard-Mastercard-Consumer-Prepaid “MCC-2-C” – Mastercard-Mastercard-Commercial-Credit “MCC-2-P” – Mastercard-Mastercard-Commercial-Prepaid “MCC-4-C” – Mastercard-Mastercard-Other-Credit “MCC-4-D” – Mastercard-Mastercard-Other-Debit “MCC-4-P” – Mastercard-Mastercard-Other-Prepaid “MSI-1-D” – Mastercard-Maestro-Consumer-Debit “MSI-1-P” – Mastercard-Maestro-Consumer-Prepaid “MSI-2-D” – Mastercard-Maestro-Commercial-Debit “MSI-2-P” – Mastercard-Maestro-Commercial-Prepaid “VIS-02-C” – VISA-VISA-Commercial-Credit “VIS-02-D” – VISA-VISA-Commercial-Debit “VIS-02-P” – VISA-VISA-Commercial-Prepaid “VIS-01-C” – VISA-VISA-Consumer-Credit “VIS-01-D” – VISA-VISA-Consumer-Debit “VIS-01-P” – VISA-VISA-Consumer-Prepaid “VPY-03-D” – VISA-VPAY-VPAY-Debit “VPY-03-P” – VISA-VPAY-VPAY-Prepaid “VSL-01-C” – VISA-VISA Electron-Consumer-Credit “VSL-01-D” – VISA-VISA Electron-Consumer-Debit “VSL-01-P” – VISA-VISA Electron-Consumer-Prepaid
productInvoiceIndicatorString “Payment Facilitator” “Sponsored Merchant” Default: “Payment Facilitator”OpcjonalnyProduct Invoice Indicator
paymentMethodTypeString “Direct Debit” “Bank Transfer” Default: “Direct Debit”WarunkowyTyp metody płatności do fakturowania submerchanta. To pole jest obowiązkowe, jeśli wskaźnik faktury to “Submerchant”
invoiceEmailString <=55WarunkowyInvoice email address. This field is mandatory if the Invoice indicator is “Sponsored Merchant”
payoutStringWarunkowyObject that defines the Payout Information. Mandatory if InvoiceIndicator is “Sponsored Merchant”
bankAccountString 26-26WarunkowySponsored Merchants bank account Mandatory if InvoiceIndicator is “Sponsored Merchant”
ibanString <=34WarunkowySponsored Merchants iban Mandatory if InvoiceIndicator is “Sponsored Merchant”
bicString 8<11WarunkowySponsored Merchants bic Mandatory if InvoiceIndicator is “Sponsored Merchant”
numDaysPayoutNumerOpcjonalnySponsored Merchants Payout Number of Days Reserved for future use.
maxPercentLowRiskExemptionsNumber <=100OpcjonalnyMaksymalny procent wyłączeń niskiego ryzyka dopuszczalny w systemie lub procesie.
scaExemptionString Default “0”OpcjonalnyThe field to evaluate SCA Exemptions must be filled with 1 to allow and 0 to not allow
typeOfIntegrationString “S2S” “SDK” “Plugin” Default “S2S”ObowiązkowyTyp integracji submerchanta
webhookNotificationStringWarunkowyObject that defines the webhook configuration details Mandatory if typeOfIntegration is “Plugin”.
typeString “URL” “Email”WarunkowyType of webhook notifications. Mandatory if typeOfIntegration is “Plugin”. If “Plugin”, the value must be “URL”
WartośćStringWarunkowyA delivery email address (for email type), or an HTTP(S) URL Mandatory if typeOfIntegration is “Plugin”
supportEmailString <=55WarunkowyAn email address to where all failed SPG Webhook calls will be reported by the end-of-day Mandatory if typeOfIntegration is “Plugin”
securityKeyString <=32OpcjonalnyPseudolosowy klucz symetryczny, który zostanie użyty do zaszyfrowania zawartości webhooka.

Below is an example of a POST request:

{
  "Shop": {
    "name": "Alma Parker",
    "address": {
      "street": "Norcop Court",
      "postalCode": "00-007",
      "locality": "Warsaw",
      "country": "616"
    },
    "email": "jondoe@gmail.com",
    "type": "Banks",
    "mcc": "5115",
    "pkd": "60m93YN",
    "invoiceIndicator": "Payment Facilitator",
    "products": [
      {
        "productId": "BLMD-PYBL-0-0",
        "productInvoiceIndicator": "Payment Facilitator"
      }
    ],
    "paymentMethodType": "Direct Debit",
    "invoiceEmail": "jonhdoe@gmail.com",
    "payout": {
      "bankAccount": "99999999999999999999999999",
      "iban": "RX89tf91aF",
      "bic": "pihezhuzhi",
    },
    "maxPercentLowRiskExemptions": "100",
    "scaExemption": "0",
    "typeOfIntegration": "S2S",
    "webhookNotification": {
      "type": "URL",
      "value": "78.89"
    },
    "supportEmail": "johndoe@gmail.com",
    "securityKey": "cefabijtakidaanogatopwazwoshawzi"
  }
}

Update shop

To update of shop details, kindly refer to the list of available environment endpoints below:

EnvironmentURLOperation Method & EndpointOperation Description
PRODapi.sibsgateway.comPUT sibs/onboarding/v1/sponsored-merchant/{merchant-id}/shop/{shop-id}Update a Merchant Establishment resource.
CERstargate-cer.qly.site1.sibs.ptPUT sibs/onboarding/v1/sponsored-merchant/{merchant-id}/shop/{shop-id}Update a Merchant Establishment resource.
Sandboxsandbox.sibsgateway.comPUT sibs/onboarding/v1/sponsored-merchant/{merchant-id}/shop/{shop-id}Update a Merchant Establishment resource.

You need to perform a PUT request including the following header and path parameters:

Parameters
ParameterTypeConditionRequiredDescription
Typ zawartościStringObowiązkowyNagłowekapplication/json
X-Request-IDStringObowiązkowyNagłowekID of the request, unique to the call, as determined by the initiating party
merchant-idStringObowiązkowyŚcieżkaID of Sponsored Merchant
shop-idStringObowiązkowyŚcieżkaID of Establishment
x-ibm-client-idStringObowiązkowyNagłowekToken that identifies a client organization. It is provided during onboarding process and must be used in every call

The table below details the parameters that can be utilized in the request message to update shop information:

Parametry żądania
Data ElementType LengthConditionDescription
shopObowiązkowyObject that defines the Merchant Establishment
addressStringOpcjonalnyEstablishment Address When these fields are empty, the value to be considered will be the ones parametrized at the Merchant level.
streetString <=100OpcjonalnyUlica
postalcodeString <=25OpcjonalnyKod pocztowy
localityString <=20OpcjonalnyMiejscowość
emailString <=55OpcjonalnyEstablishment Email When these fields are empty, the value to be considered will be the ones parametrized at the Merchant level.
phoneNumberString <=16OpcjonalnyEstablishment Phone When these fields are empty, the value to be considered will be the ones parametrized at the Merchant level.
typeString “Banks” “Wholesale“ “Supermarket“ “Retail“ “Gas Stations“ “Restaurants“ “Hotels“ “Others” “Virtual Establishment“ “Foreign“ “Service Provider“ “Service Entity“ “EMV Tolls“ObowiązkowyEstablishment Type
maxPercentLowRiskExemptionsNumber <=100OpcjonalnyMaksymalny procent wyłączeń niskiego ryzyka dopuszczalny w systemie lub procesie.
scaExemptionString Default “0”OpcjonalnyThe field to evaluate SCA Exemptions must be filled with 1 to allow and 0 to not allow

Find below a PUT request example:

{
  "Shop": {
    "address": {
      "street": "Behsu Road",
      "postalCode": "K8D 1C8",
      "locality": "aparuma"
    },
    "email": "JRvAd_GfBJs.@lLdRqk9B16A7rc7B_oBb1BNaVj1mVvx-0YEJFBRoeINdL_GhCb4x-KBYnsKjY9_9a0wnyFn7A.OdVz",
    "phoneNumber": "13881980362441110710459585739360",
    "type": "Banks",
    "maxPercentLowRiskExemptions": "100",
    "scaExemption": "0"
  }
}

Cancel shop

To remove a shop from the system based on its unique identifier, you can execute a DELETE operation. For this action, please utilize the following endpoints:

EnvironmentURLOperation Method & EndpointOperation Description
PRODapi.sibsgateway.comDELETE sibs/onboarding/v1/sponsored-merchant/{merchant-id}/shop/{shop-id}Cancel a Merchant Establishment resource.
CERstargate-cer.qly.site1.sibs.ptDELETE sibs/onboarding/v1/sponsored-merchant/{merchant-id}/shop/{shop-id}Cancel a Merchant Establishment resource.
Sandboxsandbox.sibsgateway.comDELETE sibs/onboarding/v1/sponsored-merchant/{merchant-id}/shop/{shop-id}Cancel a Merchant Establishment resource.

Find below the request headers and path:

Parameters
ParameterTypeConditionRequiredDescription
Typ zawartościStringObowiązkowyNagłowekapplication/json
X-Request-IDStringObowiązkowyNagłowekID of the request, unique to the call, as determined by the initiating party
merchant-idStringObowiązkowyŚcieżkaID of Sponsored Merchant
shop-idStringObowiązkowyŚcieżkaID of Establishment
x-ibm-client-idStringObowiązkowyNagłowekToken that identifies a client organization. It is provided during onboarding process and must be used in every call
Info

For more information related to the error messages, please refer to the page Onboarding API > Merchant, section Error handling.

Add payment method

Our API enables seamless integration of new financial products into an existing store. To add a new payment method, please refer to the list of available environment endpoints provided below:

ŚrodowiskoURLMetoda działania i endpointyOpis
PRODapi.sibsgateway.comPOST sibs/onboarding/v1/sponsored-merchant/{merchant-id}/shop/{shop-id}/productsAdd new Financial Product
CERstargate-cer.qly.site1.sibs.ptPOST sibs/onboarding/v1/sponsored-merchant/{merchant-id}/shop/{shop-id}/productsAdd new Financial Product
Sandboxsandbox.sibsgateway.comPOST sibs/onboarding/v1/sponsored-merchant/{merchant-id}/shop/{shop-id}/productsAdd new Financial Product

You need to perform a POST request including the following header and path parameters:

Parameters
ParametrTypStanRequiredOpis
Typ zawartościStringObowiązkowyNagłowekapplication/json
X-Request-IDStringObowiązkowyNagłowekID of the request, unique to the call, as determined by the initiating party
merchant-idStringObowiązkowyŚcieżkaID of Sponsored Merchant (required in the path)
shop-idStringObowiązkowyŚcieżkaID of Establishment (required in the path)
x-ibm-client-idStringObowiązkowyNagłowekToken that identifies a client organization. It is provided during onboarding process and must be used in every call

The table below details the parameters that should be included in the request message to add a financial product:

Request Parameters
Data ElementType LengthConditionDescription
productsObowiązkowyObject that defines the Establishment Products
productIdString “XPAY-APPL-0-0”, “XPAY-GGLE-0-0”, “PYWK-BNPL-1-0”, “PYWK-BNPL-2-0”, “INTP-BLIK-0-0”, “INTP-BLIK-1-0”, “BLMD-PYBL-0-0”, “KEVN-PYBL-0-0”, “MCC-1-C”, “MCC-1-D”, “MCC-1-P”, “MCC-2-C”, “MCC-2-P”, “MCC-4-C”, “MCC-4-D”, “MCC-4-P”, “MSI-1-D”, “MSI-1-P”, “MSI-2-D”, “MSI-2-P”, “VIS-01-C”, “VIS-01-D”, “VIS-01-P”, “VIS-02-C”, “VIS-02-D”, “VIS-02-P”, “VPY-03-D”, “VPY-03-P”, “VSL-01-C”, “VSL-01-D”, “VSL-01-P” “MRKP-CRTB-0-0”ObowiązkowyFinancial product to be added. Product ID’s to activate: “INTP-BLIK-0-0” InterPay-BLIK-Domestic “INTP-BLIK-1-0” – InterPay-BLIK-OneClick “BLMD-PYBL-0-0” BlueMedia-PayByLink-Domestic “KEVN-PYBL-0-0” – PayByLink-Kevin “MCC-1-C” – Mastercard-Mastercard-Consumer-Credit “MCC-1-D” – Mastercard-Mastercard-Consumer-Debit “MCC-1-P” – Mastercard-Mastercard-Consumer-Prepaid “MCC-2-C” – Mastercard-Mastercard-Commercial-Credit “MCC-2-P” – Mastercard-Mastercard-Commercial-Prepaid “MCC-4-C” – Mastercard-Mastercard-Other-Credit “MCC-4-D” – Mastercard-Mastercard-Other-Debit “MCC-4-P” – Mastercard-Mastercard-Other-Prepaid “MSI-1-D” – Mastercard-Maestro-Consumer-Debit “MSI-1-P” – Mastercard-Maestro-Consumer-Prepaid “MSI-2-D” – Mastercard-Maestro-Commercial-Debit “MSI-2-P” – Mastercard-Maestro-Commercial-Prepaid “VIS-02-C” – VISA-VISA-Commercial-Credit “VIS-02-D” – VISA-VISA-Commercial-Debit “VIS-02-P” – VISA-VISA-Commercial-Prepaid “VIS-01-C” – VISA-VISA-Consumer-Credit “VIS-01-D” – VISA-VISA-Consumer-Debit “VIS-01-P” – VISA-VISA-Consumer-Prepaid “VPY-03-D” – VISA-VPAY-VPAY-Debit “VPY-03-P” – VISA-VPAY-VPAY-Prepaid “VSL-01-C” – VISA-VISA Electron-Consumer-Credit “VSL-01-D” – VISA-VISA Electron-Consumer-Debit “VSL-01-P” – VISA-VISA Electron-Consumer-Prepaid “MRKP-CRTB-0-0” – MarketPay – Cartes Bancaires
ProductInvoiceIndicatorString “Payment Facilitator” “Sponsored Merchant” Default: “Payment FacilitatorOpcjonalnyProduct Invoice Indicator

Find below a POST request example:

{
  "products" : [ {
    "productId" : "MCC-1-C",
    "productInvoiceIndicator" : "Payment Facilitator"
  } ]
}

Delete payment method

To remove a financial product/payment method from an existing establishment, you can execute a DELETE operation. For this action, please utilize the following endpoints:

EnvironmentURLOperation Method & EndpointDescription
PRODapi.sibsgateway.comDELETE sibs/onboarding/v1/sponsored-merchant/{merchant-id}/shop/{shop-id}/productsDelete a Financial Product from an Establishment
CERstargate-cer.qly.site1.sibs.ptDELETE sibs/onboarding/v1/sponsored-merchant/{merchant-id}/shop/{shop-id}/productsDelete a Financial Product from an Establishment
Sandboxsandbox.sibsgateway.comDELETE sibs/onboarding/v1/sponsored-merchant/{merchant-id}/shop/{shop-id}/productsDelete a Financial Product from an Establishment

You need to perform a DELETE request including the following header and path parameters:

Parameters
ParameterTypeConditionRequiredDescription
Typ zawartościStringObowiązkowyNagłowekapplication/json
X-Request-IDStringObowiązkowyNagłowekID of the request, unique to the call, as determined by the initiating party
merchant-idStringObowiązkowyŚcieżkaID of Sponsored Merchant (required in the path)
shop-idStringObowiązkowyŚcieżkaID of Establishment (required in the path)
x-ibm-client-idStringObowiązkowyNagłowekToken that identifies a client organization. It is provided during onboarding process and must be used in every call

The table below details the parameters that should be included in the request message to add a financial product:

Request Parameters
Data ElementType LengthConditionDescription
productsObowiązkowyObject that defines the Establishment Products
productIdString “XPAY-APPL-0-0”, “XPAY-GGLE-0-0”, “PYWK-BNPL-1-0”, “PYWK-BNPL-2-0”, “INTP-BLIK-0-0”, “INTP-BLIK-1-0”, “BLMD-PYBL-0-0”, “KEVN-PYBL-0-0”, “MCC-1-C”, “MCC-1-D”, “MCC-1-P”, “MCC-2-C”, “MCC-2-P”, “MCC-4-C”, “MCC-4-D”, “MCC-4-P”, “MSI-1-D”, “MSI-1-P”, “MSI-2-D”, “MSI-2-P”, “VIS-01-C”, “VIS-01-D”, “VIS-01-P”, “VIS-02-C”, “VIS-02-D”, “VIS-02-P”, “VPY-03-D”, “VPY-03-P”, “VSL-01-C”, “VSL-01-D”, “VSL-01-P” “MRKP-CRTB-0-0”ObowiązkowyFinancial product to be added. Product ID’s to activate: “INTP-BLIK-0-0” InterPay-BLIK-Domestic “INTP-BLIK-1-0” – InterPay-BLIK-OneClick “BLMD-PYBL-0-0” BlueMedia-PayByLink-Domestic “KEVN-PYBL-0-0” – PayByLink-Kevin “MCC-1-C” – Mastercard-Mastercard-Consumer-Credit “MCC-1-D” – Mastercard-Mastercard-Consumer-Debit “MCC-1-P” – Mastercard-Mastercard-Consumer-Prepaid “MCC-2-C” – Mastercard-Mastercard-Commercial-Credit “MCC-2-P” – Mastercard-Mastercard-Commercial-Prepaid “MCC-4-C” – Mastercard-Mastercard-Other-Credit “MCC-4-D” – Mastercard-Mastercard-Other-Debit “MCC-4-P” – Mastercard-Mastercard-Other-Prepaid “MSI-1-D” – Mastercard-Maestro-Consumer-Debit “MSI-1-P” – Mastercard-Maestro-Consumer-Prepaid “MSI-2-D” – Mastercard-Maestro-Commercial-Debit “MSI-2-P” – Mastercard-Maestro-Commercial-Prepaid “VIS-02-C” – VISA-VISA-Commercial-Credit “VIS-02-D” – VISA-VISA-Commercial-Debit “VIS-02-P” – VISA-VISA-Commercial-Prepaid “VIS-01-C” – VISA-VISA-Consumer-Credit “VIS-01-D” – VISA-VISA-Consumer-Debit “VIS-01-P” – VISA-VISA-Consumer-Prepaid “VPY-03-D” – VISA-VPAY-VPAY-Debit “VPY-03-P” – VISA-VPAY-VPAY-Prepaid “VSL-01-C” – VISA-VISA Electron-Consumer-Credit “VSL-01-D” – VISA-VISA Electron-Consumer-Debit “VSL-01-P” – VISA-VISA Electron-Consumer-Prepaid “MRKP-CRTB-0-0” – MarketPay – Cartes Bancaires
productInvoiceIndicatorString “Payment Facilitator” “Sponsored Merchant” Default: “Payment FacilitatorOpcjonalnyProduct Invoice Indicator

Find below a DELETE request example:

{
  "products" : [ {
    "productId" : "MCC-1-C",
    "productInvoiceIndicator" : "Payment Facilitator"
  } ]
}

After the request, the API will respond with one of the two status codes:

Kod statusuWiadomośćTransactionStatus
000Sukces“ACT” (Accepted Technical Validation)
999Unexpected Error“RJT” (Rejected)
Przegląd prywatności

Ta strona korzysta z ciasteczek, aby zapewnić Ci najlepszą możliwą obsługę. Informacje o ciasteczkach są przechowywane w przeglądarce i wykonują funkcje takie jak rozpoznawanie Cię po powrocie na naszą stronę internetową i pomaganie naszemu zespołowi w zrozumieniu, które sekcje witryny są dla Ciebie najbardziej interesujące i przydatne.

Ściśle niezbędne ciasteczka

Niezbędne ciasteczka powinny być zawsze włączone, abyśmy mogli zapisać twoje preferencje dotyczące ustawień ciasteczek.