> For the complete documentation index, see [llms.txt](https://developer.paywall.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.paywall.one/payment-orchestration-integration-document/system-data/payment-statuses.md).

# Payment Statuses

<table><thead><tr><th width="172">ID</th><th>Status</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>Created</td><td><p>When transaction requests are sent to Paywall, the transaction record created in Paywall is initially recorded as <strong>Created</strong></p><p>This step represents that the transaction has been received</p><p></p><p><strong>Example</strong> When a NonSecure payment request is sent to Paywall it is first set to <strong>Created</strong> status After the payment process starts the status is updated with other states</p></td></tr><tr><td>2</td><td>Started</td><td><p>Depending on the payment method, the step at which a payment reaches the <strong>Started</strong> status may vary</p><p>Ultimately, the <strong>Started</strong> status represents the step where communication with the provider is initiated</p><p></p><p>Let’s summarize this for both NonSecure and 3D</p><p>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 </p><p><strong>Started</strong></p><p></p><p>3D When the transaction is sent to Paywall a 3D link is returned At this stage the payment remains in <strong>Created</strong> status in Paywall However once the 3D link is opened the payment status is updated to <strong>Started</strong></p></td></tr><tr><td>3</td><td>Waiting for Financialization</td><td>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 <mark style="color:blue;"><strong>Waiting</strong></mark><strong> for </strong><mark style="color:blue;"><strong>Financialization</strong></mark> status</td></tr><tr><td>4</td><td>Successful</td><td>If the transaction is completed successfully, the status of the transaction is displayed as <mark style="color:green;"><strong><code>Successful</code></strong></mark></td></tr><tr><td>5</td><td>Failed</td><td>If the transaction cannot be <mark style="color:$warning;">completed successfully</mark>, the status of the transaction is displayed as <mark style="color:red;"><strong>Failed</strong></mark></td></tr><tr><td>6</td><td>PayJump</td><td><p>If a payment fails and recovery via PayJump is initiated, the status of the payment is updated to <mark style="color:green;"><strong>PayJump</strong></mark></p><p>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</p></td></tr><tr><td>7</td><td>Failed (On Query)</td><td>If the transaction is queried on the provider side and is determined to be unsuccessful, the transaction is set to <mark style="color:red;"><code>Failed (On Query)</code></mark> status</td></tr><tr><td>8</td><td>Intermediate Transaction</td><td><p>The <strong>Intermediate Transaction</strong> status indicates that an additional step required for the transaction to be completed is currently being performed</p><p>These steps are typically token retrieval processes from the Bank/PF</p></td></tr><tr><td>9</td><td>Query Started (PayJump)</td><td><p>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)</p><p>In this case, the steps where the query starts and ends are recorded</p><p></p><p>Example Timeout transactions</p></td></tr><tr><td>10</td><td>Query Completed (PayJump)</td><td><p>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)</p><p>In this case, the steps where the query starts and ends are recorded</p><p></p><p>Example Timeout transactions</p></td></tr><tr><td>11</td><td>Provider Callback</td><td>If a notification is received from the provider where the payment was processed, the transaction is updated as <mark style="color:blue;"><code>Provider Callback</code></mark></td></tr><tr><td>12</td><td>Canceled</td><td>Pre-authorization transactions are updated to <mark style="color:red;"><code>Canceled</code></mark> when the pre-authorization is canceled</td></tr><tr><td>13</td><td>Marked as Fraud</td><td>If transactions are marked as fraud by the system or authorized users, the status of the transaction is updated as <mark style="color:red;"><code>Marked as Fraud</code></mark></td></tr><tr><td>14</td><td>Pending</td><td><p><mark style="color:$tint;"><code>Pending</code></mark> transactions indicate that the transaction is waiting for an action required by the flow</p><p>Examples</p><p>1 Masterpass 3D link opening<br>2 Masterpass OTP verification<br>etc</p></td></tr></tbody></table>