Paga Collect API

Setup

Wiring Paga Collect by hand means setting up its HTTP basic auth, choosing between the production collect.paga.com and beta hosts, and building your own retry and error handling. Through Jentic you install once, import the Paga Collect API from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

Paga Collect takes its targets in the request body rather than the URL path, so limit the agent to the operations it needs, such as creating a payment request or checking its status. Operations like issuing a refund are not included unless you add them.

Credential isolation

Your Paga Collect credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'request a payment' or 'check payment status', and Jentic returns the matching Paga Collect operation with its input schema so the agent calls the right endpoint without browsing the reference docs.