Skip to main content
TweezerComm has a resilience mechanism for handling transaction completion or cancellation in case of errors or failures. Whenever an error occurs, such as a statusCode != 0, TweezerComm automatically falls back to this mechanism, using retries and verification steps to complete or cancel the transaction and prevent inconsistencies.

​
How it works

The flow chart describes the flow of the mechanism.
When a transaction requires completion (settlement) or cancellation, the system checks whether it received a response, and the flow varies depending on the outcome.
  • If the system receives a response, it checks the StatusCode. If the value equals 0, it finishes the completion process; otherwise, it triggers the retry mechanism.
  • If the system doesn’t receive a response, it retrieves transaction details using the getTransactionByVuid() method.
    • To check whether the transaction is complete, the system evaluates whether IsFinalAmount=1 and TransactionDeposited=1/2.
    • If those values don’t match, the system triggers the retry mechanism.
The process loops back to the start of the Completion/Cancel flow until it reaches a definitive success or failure condition.

​
See also

Payment flows

See the payment flows this resilience mechanism protects.

GetTransactionByVuid

Retrieve transaction details using the vendor-unique identifier (vuid).