API Keys

PaidYET now uses Merchant-Level API Keys only.

Partner-level API keys have been deprecated to simplify integrations and reduce confusion. All new integrations should be built using merchant-level keys.

Merchant-Level API Keys

Merchant API keys are generated within each merchant’s dashboard (Settings > Developers) and are scoped specifically to that merchant.

Use these keys for all API requests related to that merchant.

Key points:

• Each key is tied to a single merchant
• No additional UUID passing is required
• Clear ownership and access control per merchant
• Recommended for all integrations going forward

Integrating Multiple Merchants

If you are integrating multiple merchants (for example, as a partner or platform):

• Generate a unique API key for each merchant
• Store and manage these keys on your end
• Route requests using the appropriate merchant’s API key

While this requires managing multiple keys, it provides:

• Better security isolation
• Simpler request structure
• More predictable behavior

Key Rotation

When rotating API keys:

• Each merchant key must be rotated individually
• We recommend building a secure key management process if handling multiple merchants

Partner API Keys (Legacy)

Existing partner API keys will continue to function, but new integrations should use merchant-level API keys. If you have a use case that may require a partner key, contact [email protected] and we’ll help guide you.