STIP(Stand-In Processing) Action
The STIP action enables Paymentology to stand in on your behalf in the event of a communication failure during transaction authorisation.
When a rule configured with the STIP action is triggered, it designates that transaction as eligible for stand-in processing.
How It Works
Under normal processing:
- A transaction is received by Paymentology.
- A FAST message is sent to the client for authorisation.
- The client performs balance checks and risk validation.
- The client responds with an approval or decline decision.
If communication with the client fails (e.g. timeout, connectivity issue, or no response to the FAST message), Paymentology is unable to obtain the client’s decision.
If the triggered rule includes the STIP action, Paymentology will: • Stand in on the client’s behalf. • Make an authorisation decision according to predefined stand-in logic. • Ensure transaction continuity despite the communication failure.
Key Purpose
The STIP action provides: • Resilience during outages or timeouts • Reduced transaction disruption • Improved cardholder experience during temporary connectivity issues
Important Notes • STIP only applies if the rule containing the STIP action has been triggered. • It does not replace normal authorisation flows. • It is only invoked when FAST communication with the client fails.
STIP actions do not need to be created or configured, as this action is inherently available to all clients by default. You only need to assign the action to a rule.
Updated 12 days ago