Requirements and permissions
- Ask Provet to enable the OAuth integration with a Client ID and Client secret, the client_credentials flow and restapi scope. The associated virtual user's permissions determine which resources it can read.
- The ImaCash computer needs outbound HTTPS access to Provet Cloud. Confirm your instance domain with Provet and compatibility with the installed version; do not change the domain or certificates to bypass errors.
- Allow read access to department, invoice, invoicepayment, unallocatedpayment and user for the relevant department. A valid token does not guarantee access to every resource. These queries do not require write permissions.
- Also request read access to the paymentmethod catalogue to identify custom methods, including custom cards. Provet must assign the appropriate catalogue permissions; do not grant general administrator access as a workaround.
Configuration in ImaCash
- Open Configuration > Integration and select Provet Cloud. The previous name Provet Cloud V2 remains only as a compatibility alias, not as a second integration.
- Provet ID (tenantId): the numeric instance or clinic identifier supplied by Provet. It is not a username, email address or department ID; enter only the identifier, not a URL.
- Client ID: the OAuth identifier of the integration enabled for that instance.
- Client secret: Private information provided by the administrator. Enter it only in ImaCash.
- Save the configuration and select the department for this till when prompted. Also review user filters and the active currency before testing.
Capture and payment methods
- ImaCash reads finalized invoices for the department, their payments and unallocated payments. Always compare amounts, currency and payment method in both systems; an API read does not confirm a physical cash movement.
- The documented standard types are payment_type=1 for cash and payment_type=0 for card. Identifying these types does not depend on a successful auxiliary paymentmethod query.