canonical: https://jentic.com/apis/paga.com/paga

# Paga Collect API

The Paga Collect API allows organizations to create persistent payment accounts and payment requests, collect payments from customers via bank transfers, USSD, cards, and offline agents in Nigeria.

## For AI agents

The Paga Collect API allows organizations to create persistent payment accounts and payment requests, collect payments from customers via bank transfers, USSD, cards, and offline agents in Nigeria.

## Scope

Provides access to Paga Collect API functionality as defined in the OpenAPI specification.

## Capabilities

- Create a payment request
- Query payment request status
- Refund a payment request (v2)
- Refund a payment request (v1)
- Get transaction history

## Use cases

### Basic Paga Collect API Integration

Integrate Paga Collect API into your application to access its core functionality.

Example prompt: Use the Paga Collect API API to access vendor services and data.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/paymentRequest` | Create a payment request |
| POST | `/status` | Query payment request status |
| POST | `/refund/v2` | Refund a payment request (v2) |
| POST | `/refund` | Refund a payment request (v1) |
| POST | `/history` | Get transaction history |
| POST | `/banks` | Get supported banks |

## Key resources

- **Main API** — Primary Paga Collect API resources and operations

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## FAQ

### What authentication does the Paga Collect API use?

The Paga Collect API uses basic authentication.

### How many endpoints does the Paga Collect API have?

The Paga Collect API has 6 endpoints available.

### Can I limit what my agent is allowed to do with the Paga Collect API?

Yes. Because you run Jentic One yourself, your own rules decide which Paga Collect operations and credentials your agent may use. You can allow only the operations it needs, such as creating a payment request or querying its status, while withholding sensitive ones like issuing a refund or pulling transaction history unless you explicitly add them. Since Paga Collect takes its targets in the request body rather than the URL path, restricting access at the operation level is how you keep the agent from calling anything you have not approved.