Payment Statuses
StatusId sent in payment inquiries and feedback
1
Created
When payment orders are submitted to Paywall, the transaction record created in Paywall is initially registered as "Created". This step indicates that the transaction has been received. Example: When a NonSecure payment order is submitted to Paywall, it is first recorded with the "Created" status. Afterwards, as the payment process begins, the status is updated to reflect the current payment stage.
2
Started
Depending on the payment method, the “Started” status may vary. This status generally represents the step where communication with the provider begins. Below is a summary for both NonSecure and 3D payment flows:
NonSecure: Once the transaction reaches Paywall, it immediately proceeds through internal checks and starts communication with the provider (Bank/PF). When the communication begins, the payment is updated to Started.
3D: When the transaction is submitted to Paywall, a 3D link is returned. At this point, the payment remains in the Created
status. Once the 3D link is opened, the payment is updated to Started
.
3
Waiting for Settlement
If the payment is a pre-authorized transaction, and the transaction is successful but waiting for the settlement (capture) command, the payment remains in the Waiting
for Settlement
status during this period.
4
successfully
If the relevant transaction is completed successfully
, its status will be displayed as Successful.
5
Failed
If the relevant transaction fails to complete successfully, its status will be displayed as Failed
.
6
PayJump
When a payment fails, the moment it starts to be recovered via PayJump, the status of the related payment is updated to PayJump. This makes it possible to identify that the payment is currently being processed by the PayJump recovery algorithm, and the subsequent transaction steps can still be tracked accordingly.
7
Failed (On Query).
If the related transaction is detected as failed at the moment it is queried on the provider side, its status will be set to Failed (On Query).
8
Intermediate
The Intermediate status indicates that an additional step required for the transaction to be completed is currently in progress. These steps are generally related to actions like token retrieval from the Bank or Payment Facilitator (PF).
9
Query Started (PayJump)
If a transaction that failed at the HTTP layer and entered PayJump is configured to allow provider-side querying in your PayJump setup, it will be queried at the relevant provider (e.g., in the case of a timeout error). In this case, the steps indicating the start and end of the query are recorded.
Example: Timeout transactions.
10
Query Completed (PayJump)
If a transaction has failed at the HTTP layer and has entered PayJump, and if your PayJump configuration has provider-side querying enabled, the transaction will be queried at the relevant provider (e.g., in the case of a timeout error). In such cases, the steps indicating when the query started and ended are logged.
Example: Timeout transactions.
11
Sağlayıcı Geri Bildirim → Provider Callback
If a notification regarding the transaction is received from the Provider, the transaction is updated as Provider Callback
.
12
Canceled
Transactions in pre-authorization are updated to Canceled when the pre-authorization is canceled.
13
Marked as Fraud
If a transaction is marked as fraud by the system or authorized users, its status is updated to Marked as Fraud.
14
Pending
Pending
transactions indicate that the transaction is waiting for an action required by the flow.
Examples:
Opening of the Masterpass 3D link
Masterpass OTP verification etc.
Last updated