Skip to main content

Generating Production API Keys and Secrets

Allyn Neal
  • Updated
Once Tillo confirms that your API certification has been approved, follow these steps.
 

1. Activate your Buyer Hub access

  1. Look for an invitation email indicating you have been set up with a Tillo account.
  2. Open the invitation and create your password and configure your 2FA.
  3. Sign in at app.tillo.io
  4. Confirm that you are working in the Production environment—not Sandbox.
  5. If you cannot see the production account or API Admin, contact your Tillo Implementation Consultant. Admin users can also control API Admin permissions in the hub. 
example.png​
Sandbox and Production are separate environments. Credentials and IP addresses configured in Sandbox do not automatically carry over to Production.

 

2. Check your company and user details

  1. Open your company/profile settings.
  2. Check the company name, address, support details and other required fields.
  3. Add any colleagues who need Hub access.
  4. Give API administration access only to trusted technical team members.
⁠⁠​

3. Create new production API credentials

From the left-hand navigation, find API Admin.
 
You will see API accounts under the Users tab. 

 

From within a user, generate new credentials using the "create access key" button.

Screenshot 2026-09-10 at 3.33.32 PM.png
Give the credentials a recognizable name, such as:
  • Production API
  • Production Primary
  • Production – [application name]
Copy both values:
- API key
- API secret
Save them immediately in a secure system.
 
Do not reuse the Sandbox key and secret. Buyers generate their API key and secret in their own Hub, and both are used as part of authenticating API requests.
⁠⁠​
Security guidance
  • Never send the secret through ordinary email or Slack.
  • Never store it in source code, tickets, spreadsheets or shared documents.
  • Restrict access to the smallest possible technical group.
  • Treat the secret like a password.
  • If it is exposed, generate replacement credentials and retire the compromised set.

 

4. Add the production IP addresses

You must be an API Admin to manage the allowlist.
  1. In the Production Hub, go to API Admin.
  2. Open the IP whitelist tab.
  3. Select the green + button.
  4. Enter the public, static outbound IP address from which your production API requests will originate.
  5. Add a note identifying the server or service.
  6. Select Add Address.
  7. Repeat for every production IP your systems may use.
  8. Confirm the addresses appear in the live list.
The address becomes active immediately. Only public addresses need to be entered; private/internal addresses do not. If your public IP changes regularly, use a stable egress IP or VPN. An address added in Production applies only to Production—it does not update Sandbox.
 
API requests from an address not on the production allowlist will be rejected, even if the API key and signature are correct.⁠⁠⁠​

 

5. Configure authentication in your application

  1. Update your application to use the production API credentials.
  3. Build the request signature using:
    1. The production API secret
    2. The fields specified for that endpoint, such as the client request ID and brand
    3. The exact field order described in the documentation
  4. Include the production API key and generated signature in the required request headers.
  5. Use the Tillo API reference and examples to confirm the required request format.
The signature changes according to the transaction type. Requests and signature inputs must match the documented format and order; malformed signatures are rejected without detailed security information.
⁠⁠​

6. Run a controlled production test

Before submitting a real-value order:
  1. Confirm that your request is leaving from an allowlisted IP.
  2. Confirm that your application is using the production key and secret.
  3. Make a permitted non-transactional request, such as retrieving available brands or account information.
  4. Check that the response is successful.
  5. If authentication fails, check:
  • You have not mixed Sandbox and Production credentials.
  • The request originates from the correct public IP.
  • The signature fields are in the documented order.
  • There are no spaces, encoding changes or formatting errors in the signature input.
  • The system clock is accurate if the request includes a timestamp.
 

7.  Confirm the account is Live and Ready to Transact with Tillo.⁠⁠⁠⁠​

Tillo must enable the buyer in Production before the account can be funded. Production credentials, IP allowlisting, certification, funding and Tillo’s final pre-launch checks must all be completed before live transactions begin.⁠⁠​

 
 
 

Related to

Related articles

Comments

0 comments

Article is closed for comments.