Shop/terminal needs to authenticate itself to SONECT. The flow will follow the “Client credentials grant” - the simplest of all the OAuth 2.0 grants and is suitable for machine-to-machine authentication where a specific user’s permission to access data is not required.
- [Confirm Transaction](https://docs.sonect.io/api-reference/API/confirm_transaction.md):When a user sends a request and shows the barcode, client will scan it. The barcode is the transaction-id. When the cashier scans the barcode, he/she is confirming the transaction.
- [Create a new user](https://docs.sonect.io/api-reference/API/create-a-new-user.md):Create a new user. Must pass your global (i.e. client) access_token.
This service returns the user's password as plain text.
The automatic update of the user's bank connections is disabled by default for any new user. User identifiers are regarded case-insensitive by finAPI.
P… - [Get Transaction](https://docs.sonect.io/api-reference/API/get_transaction.md):
When the shop scans the barcode, partner can send the transaction ID to Sonect to get transaction details such as the amount. The cashier can then decide to reject or confirm the transaction.
- [Link transaction](https://docs.sonect.io/api-reference/API/link_transaction.md):Once the transaction is confirmed, POS calls Sonect to share its internal ID for reconciliation purposes. The cashier clicks on OK on the POS interface which would then open the till. This API is crucial as it signals to Sonect if the cashier was able to hand out the money successfully to the use… - [Partner Checkin](https://docs.sonect.io/api-reference/API/partner-checkin.md): Perform oauth2 authentication and return user status and destination url. - [Reject transaction](https://docs.sonect.io/api-reference/API/reject_transaction.md):
When a user confirms the transaction, there might be cases where the user needs to perform SCA on his bank app. In this case, the POS will have to reject the transaction if the user is not performing the SCA on time. We suggest the POS sets a default timeout on its side. Sonect will set a timeout… - [Settle order](https://docs.sonect.io/api-reference/API/settle-order.md): Confirms transaction is finalised and payment should be made to given Sonect account. If response is positive then transaction is created presented to user. If negative transaction is not created. - [Start order](https://docs.sonect.io/api-reference/API/start-order.md): Informs the integrating partner that a transaction is initiated for a given amount. If response is positive funds are considered secured, but payment is not yet executed. - [Introduction](https://docs.sonect.io/api-reference/Sonect/Introduction.md) - [WebSDK Integration](https://docs.sonect.io/api-reference/Sonect/WebSDK_Integration.md) ## OpenAPI Specs - [13](https://docs.sonect.io/13.yml) - [5](https://docs.sonect.io/5.yml) - [6](https://docs.sonect.io/6.yml) - [8](https://docs.sonect.io/8.yml) - [9](https://docs.sonect.io/9.yml) - [4](https://docs.sonect.io/4.yml) - [26](https://docs.sonect.io/26.yml) - [27](https://docs.sonect.io/27.yml) - [28](https://docs.sonect.io/28.yml) - [3](https://docs.sonect.io/3.yml) - [25](https://docs.sonect.io/25.yml) - [19](https://docs.sonect.io/19.yml) - [21](https://docs.sonect.io/21.yml) - [22](https://docs.sonect.io/22.yml) - [23](https://docs.sonect.io/23.yml) - [12](https://docs.sonect.io/12.yml) - [15](https://docs.sonect.io/15.yml) - [16](https://docs.sonect.io/16.yml) - [17](https://docs.sonect.io/17.yml) - [18](https://docs.sonect.io/18.yml) - [11](https://docs.sonect.io/11.yml) - [1](https://docs.sonect.io/1.yml) - [10](https://docs.sonect.io/10.yml)