Obligation Assumption Mechanism & reimbursement via receipts

1. What is Obligation Assumption Mechanism?

The Obligation Assumption Mechanism (OAM) is a structure where Stebby takes over the client’s obligation for a short period of time to reimburse the receipt uploaded to the platform by the end-user.

The OAM is based on the Law of Obligations Act of Estonia § 175(2) for the clients registered in Estonia, Art.1876 Paragraph 2 of the Latvian Civil Law for the clients registered in Latvia and Art. 6.116(1) of the Civil Code of the Republic of Lithuania for the clients registered in Lithuania.

This allows a third party (Stebby) to take over the obligation of an obligor (client) on the basis of a contract (Obligation Assumption Framework Agreement which is an Annex 2 to the Client Terms and Conditions) in a condition that the obligee (the end-user) consents to such takeover.

The end-user gives the required consent when it uploads a receipt to the platform and before the receipt is made available for approval for the client.

The terms and conditions of the OAM are agreed in the Obligation Assumption Framework Agreement which is an Annex 2 to the Client Terms and Conditions.

2. When is Obligation Assumption Mechanism applied?

The Obligation Assumption Mechanism (OAM) is applied when the client wants to reimburse the end-user for the services provided by the third-party service providers not registered on the platform. Allowing to reimburse such receipts is optional and the function can be turned off.

3. Why is Obligation Assumption Mechanism introduced?

The Obligation Assumption Mechanism (OAM) was introduced in 2025 to ensure that Stebby can enable reimbursement of receipts in compliance with the law.

In particular, it addresses how payments are handled when reimbursing users for receipts. By formally assuming the obligation to reimburse end-users on behalf of clients, Stebby can continue offering this feature while maintaining regulatory compliance and safeguarding all parties involved.

What changed compared to before? Technically, nothing has changed for the client in terms of how they use the platform. The clients will continue using the receipt reimbursement feature as before. We have simply specified the legal structure for the receipt reimbursement process: Stebby now assumes the obligation to reimburse end-users on behalf of the client, under a specific agreement (the Obligation Assumption Framework Agreement).

4. Are there any fees related to Obligation Assumption Mechanism?

No, there is no extra fee for using the Obligation Assumption Mechanism (OAM).

The OAM cost is included in the Platform Fee, whether or not you allow the receipt compensation option.

The term “Assumption Agreement Price” in the Client Terms and Conditions means the value of the obligation itself, not an additional charge. For example: If the end-user requests reimbursement of EUR 20, Stebby assumes the obligation from you for EUR 20 (the same amount owed to the user). 

5. Is there anything I need to do in order to use the Obligation Assumption Mechanism?

Simply make sure you have thoroughly read, understood and agreed to the Client Terms and Conditions, and allowed the receipt reimbursement on the platform.

6. What to do if I do not want to use Obligation Assumption Mechanism?

If you prefer not to have the Obligation Assumption Mechanism (OAM) and the related Obligation Assumption Framework Agreement terms apply to you, you can disable the option for end-users to upload receipts. This way, end-users will only be able to purchase services from providers registered on the platform.