​

paywise Make Integration

The paywise app for Make connects the Case Management API to your Make scenarios. You can create orders and claims, read cases, report payments, download statements and start a scenario instantly when something changes in paywise, without writing code.

​

Availability

The paywise app for Make is available through an invite link while Make reviews it for its public app directory. To get the invite link, contact our support team at [email protected].

​

Connect paywise to Make

1. In paywise, open Für Entwickler and create an API key. Select only the permission scopes that your scenarios need.
2. In your Make scenario, add a paywise module and click Create a connection.
3. Paste the API key and save.

Make checks the key right away and names the connection after the key and its environment, for example my-key (sandbox). Sandbox. Sandbox keys start with pw_sbx_. A connection made with a sandbox key talks to the sandbox automatically; you do not enter a URL. Build and test your scenarios with a sandbox key first. See Sandbox. Scopes. Each module needs the scope of its group, for example order scopes for the Orders and Claims modules and payment scopes for the Payments modules. A module whose scope is missing fails with a 403 error. Triggers additionally need case:webhooks:write, because they register a webhook endpoint in paywise. “Get API key info” shows the name, environment and scopes of the connected key.

​

Modules

“Make an API call” sends any authorized request to the paywise API. Use it for operations that have no dedicated module.

​

Triggers

All triggers are instant: paywise calls Make as soon as the event happens, so there is no polling interval.

• Watch events lets you pick one or more of the case events.
• The six dedicated triggers (order decisions, case status updates, payments, statements, single case statements, requests to client) have fixed events and need no setup beyond the connection.

Each trigger outputs the event (event_id, event_type, created_at, data) and, where there is one, the referenced resource as resource, loaded with your key. For the events themselves, see Webhook events.

​

Webhook endpoints in paywise

Creating the webhook in a Make trigger registers an endpoint whose description starts with Make: in paywise. Deleting the webhook in Make removes that endpoint again. A company can have up to 20 webhook endpoints. Endpoints that paywise disabled automatically after repeated failed deliveries do not count toward this limit. If creating a trigger fails with webhook_limit_reached, or because an endpoint for the same Make URL still exists, delete unused endpoints in the paywise portal under Für Entwickler → Webhooks. To change the events of Watch events, create a new webhook in the trigger and delete the old one on Make’s Webhooks page.

​

Safe retries with an idempotency key

Every module that creates something has an optional Idempotency key field. If Make repeats a request, for example after a timeout, paywise returns the original result instead of creating a second record, as long as the key and the request are the same. If you leave the field empty, the default key changes with every run, so a retry can create a duplicate. Map a value that is unique and stable per record instead, for example your invoice number or the execution ID of the scenario combined with your own reference. See Errors and safe retries.

​

Troubleshooting

Every error message in Make ends with the paywise request ID (request <id>). Include it when you contact support.

​

Support

If you encounter any issues or have questions about the paywise Make integration, please contact our support team at [email protected]. For more information about our APIs, please refer to:

• Case Management API Documentation
• Webhooks