Skip to main content

Obtaining Credentials

To access Tumipay’s APIs you must request credentials from our support team. Send an email to [email protected] with your company details. After verification you will receive:
  • A username and password for Basic Authentication.
  • A merchant token provided as the Token-Top value.
Tokens remain valid until they are rotated or revoked. If your token is at risk of exposure or requires renewal, please contact Tumipay support.

Basic Authentication

Every API call uses HTTP Basic Auth. Combine your username and password and encode them in Base64:
# Method 1: Using curl built-in basic auth
curl -u "username:password" \
  -H "Token-Top: your_access_token" \
  -H "Content-Type: application/json" \
  https://api-empresas.staging.tumipay.co/production/api/v1/merchant/me

# Method 2: Manual base64 encoding
curl -H "Authorization: Basic $(echo -n 'username:password' | base64)" \
  -H "Token-Top: your_access_token" \
  -H "Content-Type: application/json" \
  https://api-empresas.staging.tumipay.co/production/api/v1/merchant/me
The Authorization header must accompany all requests.

Token Authentication

Most endpoints also require the merchant’s token in the Token-Top header:
Token-Top: your_access_token
Treat this token as a secret. Store it securely and rotate it regularly.

Token Renewal

Tokens do not expire automatically. If you suspect compromise, or as part of routine security maintenance, contact Tumipay support to issue a new token. Update your systems to use the new value immediately.

Required Headers

Include the following headers in requests:
Authorization
string
required
Basic credentials in the format Basic base64(username:password)
Token-Top
string
required
Your merchant authentication token
Content-Type
string
required
application/json

Security Best Practices

  • Use HTTPS for every request.
  • Keep your username, password and token in a secure environment variable or secret manager.
  • Rotate credentials periodically and revoke them immediately if exposed.
  • Never commit credentials or tokens to public repositories or client-side code.