What authentication does the PayRetailers API use?

The PayRetailers API uses dual authentication combining HTTP Basic Auth (username and password) and an API key header. Both are required for each request. Through Jentic, both credential types are stored encrypted in your Jentic One instance and agents receive scoped access without handling raw credentials.

Which payment methods are available in Brazil through PayRetailers?

Use GET /payment-methods with a country filter for Brazil to retrieve available options. Common Brazilian methods include PIX (instant bank transfer), Boleto Bancario (bank slip), and local credit card processing. Availability depends on your merchant account configuration.

How do I send a payout through Jentic?

Use Jentic to search for 'send a payout in Latin America', load the schema for POST /payouts, and execute with the destination bank account details, amount, and country. Before executing, you can get a rate quote via POST /payout-quotes and verify funds via GET /balance.

What countries does PayRetailers support?

PayRetailers covers multiple Latin American markets including Brazil, Mexico, Colombia, Argentina, Chile, Peru, and Ecuador. The GET /payment-methods endpoint returns country-specific available methods based on your merchant configuration.

Can I create recurring payment collections with PayRetailers?

Yes. By creating customer profiles via POST /customers and assigning virtual accounts through POST /customers/{customerId}/virtual-accounts, you can set up automated payment matching for recurring collections. Virtual accounts receive deposits that are automatically linked to the correct customer.

Can I limit what my agent is allowed to do with the PayRetailers API?

Yes. Because you run Jentic One yourself, you decide exactly which PayRetailers operations your agent can call and which credentials it may use. Since PayRetailers passes transaction and payout targets through the request body rather than the URL path, you scope by operation, so you can grant read-only calls like listing payment methods with GET /payment-methods or querying a transaction with GET /transactions/uid/{uid} while withholding write operations such as POST /payouts or POST /customers. Your own rules govern the set, so those write endpoints stay unavailable to the agent unless you explicitly add them.