# Payment Session State Model
For the easiest integration we have designed the session status model to be similar to other payment channels that the e-shop integrates with.
<br>
<p align="center">
<img src="/static/epos-payment-session-state-model.svg" style="width: 440px;"/>
</p>
<br>
| <b>Status</b> | <b>Description</b> |
|  --- | --- |
| <p>pending</p><p></p> | A session is created;<br>The application may be or not be in progress;<br> Positive decisions remain in this status until the contract is concluded or until they expire. |
| cancelled | The customer has cancelled the process. |
| <p>granted </p><p></p> | Rental has been granted to the customer, customer has made the first payment, there are no obstacles from the Inbank side for sales completion. The process is awaiting device identifiers after rental package is issued for customer and contract activation. |
| <b>completed</b> | This is the target state: the contract between customer and Inbank has been activated, partner is liable for the delivery of goods/services. |
| declined | Rental was declined by Inbank. |
| expired | The session was not completed during the defined time period. |

The integration flow requires a final partner-side confirmation step about device handover to the customer in Partner Portal or over API, before the application process is completed.
This may be handy if the stock is limited and the partner does not allocate stock items before it is ensured that the customer can get the rental. If the partner does not send the final approval (i.e. items are out of stock, order can not be completed), the rental agreement is not completed.