canonical: https://jentic.com/apis/sandbox-pgw.2c2p.com/sandbox-pgw-2c2p

# Sandbox Pgw 2c2p PGW Payment API 4.3

Rest API for PGW payment purpose - LATEST. The API exposes 22 endpoints.

## For AI agents

Programmatically cardinstallmentplaninfo_create, jwt request endpoint. Covers 22 operations.

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- CardInstallmentPlanInfo_create
- JWT Request Endpoint
- APM MCC Exchange Rate
- Query and filter PGW Payment API 4.3 records by parameters
- Monitor PGW Payment API 4.3 operational status and events

## Use cases

### Payments Operations

Use the PGW Payment API 4.3 to perform payments operations programmatically. The API provides 22 endpoints covering core functionality including cardinstallmentplaninfo_create, jwt request endpoint, apm mcc exchange rate.

Example prompt: Call POST `/payment/4.3/cardinstallmentplaninfo` to cardinstallmentplaninfo_create

### Automated ExchangeRate Management

Automate exchangerate operations by combining multiple PGW Payment API 4.3 endpoints. Agents can jwt request endpoint and then apm mcc exchange rate in a single workflow.

Example prompt: Call POST `/payment/4.3/exchangerate/secure` to jwt request endpoint, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call PGW Payment API 4.3 endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Example prompt: Search Jentic for 'cardinstallmentplaninfo_create', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/payment/4.3/cardinstallmentplaninfo` | CardInstallmentPlanInfo_create |
| POST | `/payment/4.3/exchangerate/secure` | JWT Request Endpoint |
| POST | `/payment/4.3/exchangerate/apmmccexchangerate` | APM MCC Exchange Rate |

## Key resources

- **ExchangeRate** — Operations related to ExchangeRate
- **ApplePay** — Operations related to ApplePay
- **Cache** — Operations related to Cache
- **CancelTransaction** — Operations related to CancelTransaction
- **CardInstallmentPlanInfo** — Operations related to CardInstallmentPlanInfo

## Why Jentic

- **Setup:** Wiring the 2C2P PGW Payment API by hand means signing each payload for the sandbox-pgw.2c2p.com host, matching the 4.3 payment payload formats, and handling retries yourself. Through Jentic you install once, import the PGW Payment API from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** The PGW Payment API sends its payment targets in the request body rather than the URL path, so limit the agent to the operations it needs, such as retrieving installment plan info or exchange rates. You choose that allowed set, so operations you do not add stay out of reach.
- **Credential handling:** Your 2C2P 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 'get card installment plan info' or 'get an exchange rate', and Jentic returns the matching PGW Payment API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the PGW Payment API 4.3 use?

The PGW Payment API 4.3 uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I cardinstallmentplaninfo_create with the PGW Payment API 4.3?

Yes. Use the POST `/payment/4.3/cardinstallmentplaninfo` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the PGW Payment API 4.3?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I cardinstallmentplaninfo_create through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'cardinstallmentplaninfo_create'. Jentic returns the matching PGW Payment API 4.3 operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the PGW Payment API 4.3 have?

The PGW Payment API 4.3 exposes 22 endpoints covering exchangerate, applepay, cache operations.

### Can I limit what my agent is allowed to do with the PGW Payment API 4.3?

Yes. Jentic One is self-hosted by you, so your own rules decide which PGW Payment API 4.3 operations and credentials the agent can use. Because this API sends its payment targets in the request body rather than the URL path, you scope access by choosing the exact operations to add, such as retrieving card installment plan info or fetching an exchange rate. Any operation you do not add, including the JWT request endpoint, stays out of the agent's reach.