7.3. Transaction Statuses And Types

Transaction Types

GitPay Payment Gateway divides all transactions into several types, depending on the purpose of each transaction. Each transaction has a specific status.

sale	Acceptance of payment for provided goods or services in a single operation.
preauth	Blocking of a fixed amount of money on the card for the subsequent withdrawal (financial pledge). The cardholder will not be able to use the held funds, however, this money will not be withdrawn from the bank account until a subsequent request (capture) is received from the merchant. After a certain period of time, if a follow-up request is not received from the merchant, the holding of this funds amount is cancelled and it will become available for use again.
capture	Withdrawal of the previously held by “preauth” transaction funds from the cardholder bank account.
cancel	Cancellation of fund holding by “preauth” transaction.
reversal	A refund operation for previously approved transaction (“sale” or “preauth” followed by “capture”). For example, a cancellation of an order by the customer, or a partial return of goods to the store.
transfer	Peer-to-peer (p2p) transfer transaction between 2 cards. This transaction can be split into 2 separate steps in some cases - card2account and deposit2card.
chargeback	Forced refund operation initiated by the cardholder, or the issuing bank, in case of fraud.
fraud	Special marker for fraudulent transactions.
retrieval	Request of additional documents for disputed or suspicious payment. Documents can be requested from the merchant or from their agent (service provider).
account verification	Validation of Payer’s card account information.
payout	Transfer of funds from merchant account to customer (receiver) banking account or digital wallet.

Transaction Statuses

All transactions are marked according to their statuses:

	Approved transaction	The transaction was processed by the acquirer successfully (payment was made as part of the transaction). Final status.
	Declined transaction	For any technical reason the acquirer cannot process the transaction. For example, this may be caused by insufficient funds on the customer card or account. Final status.
	Filtered transaction	The transaction was filtered by GitPay Payment Gateway and was not processed. Final status.
	Error	Processing of transaction failed. A second attempt can be made to process the transaction. If the error occurs again, contact the GitPay support service. Final status.
	Unknown	Payment Gateway failed to get final transaction status. Contact the GitPay support service to clarify the transaction status. Non final status.
	Failed	System’s internal status. It means there are no available settings to route transaction in the system due to filters or other restrictions. Final status.
	Processing	Transaction is being processed. If transaction status haven’t been changed for one hour - something went wrong, please inform Payment Gateway support service. Non final status.

Note

After reconciliation transaction status could be changed even if transaction is in final status.