Payment Statuses

StatusId sent in payment queries and callbacks

ID	Status	Description
1	Created	When transaction requests are sent to Paywall, the transaction record created in Paywall is initially recorded as Created This step represents that the transaction has been received Example When a NonSecure payment request is sent to Paywall it is first set to Created status After the payment process starts the status is updated with other states
2	Started	Depending on the payment method, the step at which a payment reaches the Started status may vary Ultimately, the Started status represents the step where communication with the provider is initiated Let’s summarize this for both NonSecure and 3D NonSecure When the transaction reaches Paywall it starts immediately after the necessary checks and communication is established with the provider (Bank/PF) At the moment this communication begins the payment status is updated to Started 3D When the transaction is sent to Paywall a 3D link is returned At this stage the payment remains in Created status in Paywall However once the 3D link is opened the payment status is updated to Started
3	Waiting for Financialization	If the payment is a pre-authorization transaction, after the transaction is successfully completed and while waiting for the pre-authorization closing instruction, the payment remains in Waiting for Financialization status
4	Successful	If the transaction is completed successfully, the status of the transaction is displayed as Successful
5	Failed	If the transaction cannot be completed successfully, the status of the transaction is displayed as Failed
6	PayJump	If a payment fails and recovery via PayJump is initiated, the status of the payment is updated to PayJump This allows you to identify that the payment is currently being processed by the PayJump recovery algorithm and to continue tracking the subsequent steps of the transaction
7	Failed (On Query)	If the transaction is queried on the provider side and is determined to be unsuccessful, the transaction is set to Failed (On Query) status
8	Intermediate Transaction	The Intermediate Transaction status indicates that an additional step required for the transaction to be completed is currently being performed These steps are typically token retrieval processes from the Bank/PF
9	Query Started (PayJump)	If a transaction fails at the HTTP layer and enters PayJump, and if your PayJump configuration has the provider query feature enabled, the transaction is queried on the relevant provider side (e.g., timeout error) In this case, the steps where the query starts and ends are recorded Example Timeout transactions
10	Query Completed (PayJump)	If a transaction fails at the HTTP layer and enters PayJump, and if your PayJump configuration has the provider query feature enabled, the transaction is queried on the relevant provider side (for example timeout errors) In this case, the steps where the query starts and ends are recorded Example Timeout transactions
11	Provider Callback	If a notification is received from the provider where the payment was processed, the transaction is updated as Provider Callback
12	Canceled	Pre-authorization transactions are updated to Canceled when the pre-authorization is canceled
13	Marked as Fraud	If transactions are marked as fraud by the system or authorized users, the status of the transaction is updated as Marked as Fraud
14	Pending	Pending transactions indicate that the transaction is waiting for an action required by the flow Examples 1 Masterpass 3D link opening 2 Masterpass OTP verification etc