Skip to content

Implementation

Notice

Card is a synchronous payment that allows the Client to pay to the Merchant through a banking card by inserting the Name, Card Number, Expiring date and CVV.

Front office operations

The SIBS Gateway supports two types of operations, purchases and authorisations, where the purchase triggers the payment immediately and the authorisation keeps the amount captive until a capture is performed. 

Purchase: This transaction allows a Cardholder to pay for a good or service via an electronic operation that debits his account and will credit the Acceptors banking account. Consists in an immediate debit in the Client account and it is an effective payment on the moment of the transaction. 

Authorisation: Consists in an authorisation for a future payment. It allows the Merchant to get an authorisation from the Issuer keeping the amount captive in the Cardholders banking account; the transaction is authorised and the purchase will be triggered in a second moment, when the merchant needs to trigger a “Capture” on the Backoffice. 

Backoffice operations

At a back-office level, Cards supports the following types of operations: 

Capture

Used when the Cardholder has provided an authorisation for the payment on a 1st stage and the amount is captured. Used on a 2nd stage to execute the payment, which can happen in different ways (always triggered over an authorisation): 

  • Full: capture the full amount authorised and finish the purchase; 
  • Partial: split the capture and do several payments up to the total amount authorised. 
Refund

The purpose of this operation is to refund the amount of a previous payment, crediting the Cardholder account and debiting the Merchant account. A refund can be: 

  • Full: when the total amount of the purchase is refunded to the Cardholder; 
  • Partial: when a subtotal of the total purchase is refunded to the Cardholder. 
Cancellation

Requests the cancellation of the amount (full or partial) of a previous authorisation. 

Merchant Initiated Transaction 

The purpose of this operation is to allow the Merchant to charge a service. In the first stage the Cardholder requests to register the payment as a Cardholder Initial Transaction and authorise the Merchant to do future debits (Merchant Initiated Transactions) in accordance with the service. 

Cardholder Initiated Transaction: needed to register as initial conditions. Authentication and consent collected from Cardholder.

Merchant Initiated Transaction: triggers following payments. 

Currently, two types of Merchant Initiated Transactions are accepted: 

  • Recurring: Transactions processed at fixed, regular intervals not to exceed one year between Transactions, representing an agreement between a Cardholder and a Merchant to purchase goods or services provided over a period of time; 

  • Unscheduled Card On File: A transaction using a stored credential for a fixed or variable amount that does not occur on a scheduled or regular occurring transaction date, where the Cardholder has provided consent for the Merchant to initiate one or more future transactions that are not initiated by the Cardholder.

It is possible to establish the relationship below among the Front office & Backoffice operations, having in mind that Backoffice operations will act on the Front office operations: 

PurchaseAuthorisationCapture
Capture1
Refund43
Cancellation2
  1. A capture can act over an authorisation of the total or partial amount; 
  2. An authorisation can be cancelled and the amount kept on hold will be released; 
  3. An effective payment through a capture can only be refunded; 
  4. An effective purchase only allows to trigger a refund in the Backoffice;