Drop developers

Environments

Drop keeps production access controlled and tied to verified accounts, credentials, and operational readiness.

Production

Production access is issued only to approved accounts with the right operational and billing setup.

Testing guidance is provided privately so merchants can validate the intended workflow before going live.

Each environment should use separate credentials and clear ownership so access can be revoked or rotated safely.

Before production use, teams should know who monitors delivery activity, webhooks, and exception handling.

Access notes

Drop does not publish environment base URLs or credential examples in public docs.

Environment-specific details are shared in verified merchant workspaces.

Private implementation

Detailed request examples, credentials, webhook verification material, and production setup steps are shared only inside verified Drop accounts.