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 Source: https://docs.sonect.io/api-reference/API/confirm_transaction 13 post /transaction/confirmWhen 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 Source: https://docs.sonect.io/api-reference/API/create-a-new-user 13 post /api/v2/usersCreate 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.
Please note that finAPI generally has a restricted set of allowed characters for input fields. You can find the allowed characters here. If a field does not explicitly specify a set of allowed characters, then these are the characters that are allowed for the field. Some fields may specify a different set of characters, in which case this will be documented for the field (like for the 'id' field in this service).
# Get Transaction Source: https://docs.sonect.io/api-reference/API/get_transaction 13 get /transaction?id=transaction_idWhen 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 Source: https://docs.sonect.io/api-reference/API/link_transaction 13 post /transaction/linkOnce 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 user. If the transaction is missing the POS ids, Sonect will investigate during reconciliation.
# Partner Checkin Source: https://docs.sonect.io/api-reference/API/partner-checkin 13 post /api/v7/partnerCheckin Perform oauth2 authentication and return user status and destination url. # Reject transaction Source: https://docs.sonect.io/api-reference/API/reject_transaction 13 post /transaction/rejectWhen 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 after 40 sec and will then set the transaction status to canceled.
# Settle order Source: https://docs.sonect.io/api-reference/API/settle-order 13 post /api/sonect/settlewithdrawal 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 Source: https://docs.sonect.io/api-reference/API/start-order 13 post /api/sonect/startwithdrawal 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. # null Source: https://docs.sonect.io/api-reference/Sonect/Introduction SONECT is a payment system which provides CASH Withdrawal. We perform the following: 1. Partner onboarding 2. Merchant onboarding 3. Users registration 4. Merchant Products * Native App: This solution allows customers to issue barcodes via an integrated payment method. User-friendly and convenient, the Native App is designed with the end-user in mind. * WebSDK: This versatile solution allows for the issuing of barcodes within a browser setting, ensuring wider compatibility across devices. As a Sonect-preferred product on the consumer side, it combines convenience with extensive support. # null Source: https://docs.sonect.io/api-reference/Sonect/WebSDK_Integration The enclosed document describes how to integrate the SONECT SDK into another app. It includes instructions for the following: * Android * iOS * Hybrid applications * Backend (Server-to-server / Webhooks) Get Sonect SDK Documentation PDF [here](https://storage.googleapis.com/documentation-storage-sonect/WebSDK-Integration-Documentation.pdf)