Welcome to the Mint Payments Integration FAQ. This page covers the most common questions that arise during the integration process — from getting started and authentication, through to payments, tokenisation, reconciliation, and troubleshooting.

If you can't find what you're looking for here, please don't hesitate to reach out to your account manager or contact our support team directly.

Getting Started

1. How do I get API credentials or access to start integrating?

You'll need your API credentials (e.g. bearer token, API key, secret key) along with the correct endpoints (sandbox or production). Contact support or your account manager to have these generated and securely shared.

2. Can I get access to a sandbox or test environment?

Yes. Mint provides a sandbox/UAT environment for testing before going live. You can request sandbox credentials and confirm activation with support.

3. How do I move from sandbox to production?

Once testing is complete, you'll need production credentials and confirmation of go-live readiness. Mint will guide you through enabling live processing and switching endpoints.

Tip: Make sure to complete all sandbox testing and obtain sign-off before requesting production credentials.

Integrations & Setup

1. Can you set up or enable an integration for our system?

Yes. Mint supports integrations with a wide range of travel platforms. Refer to the integrations list on our website, or contact your sales or customer service representative for the full list. If you already have a platform in mind, let our team know and we can help set you up.

2. Can Mint integrate with our website or custom checkout?

Yes. You can integrate via API, hosted payment pages, or embedded checkout flows. Mint also supports common ecommerce platforms and custom-built solutions. See our getting started page for details about which integration method is best for you.

3. How do I confirm I'm using the correct API endpoint or webhook URL?

Ensure you're using the correct base URL (sandbox vs. production), along with the appropriate callback/webhook endpoints. If you're unsure, our support team can validate your configuration.

Important: Always double-check that your environment (sandbox or production) matches your API credentials and endpoint URLs. Mismatches are a common source of errors.

Authentication & Access Issues

1. Why am I getting authentication errors (403, Access Denied, invalid token)?

These errors typically indicate incorrect credentials, expired tokens, or insufficient permissions. Double-check your keys and environment, or contact support to verify access. For more details, refer to our Understanding Error Codes documentation.

2. Do I need to whitelist IPs or adjust security settings?

In some cases, yes. If your requests are being blocked, you may need to whitelist specific IP addresses or adjust firewall/WAF settings to allow traffic to reach Mint's endpoints. Contact support for the current list of IPs to whitelist.

Payments & Checkout Issues

1. Why is the Hosted Payment Page (HPP) or payment link not working?

This may be due to incorrect configuration, expired links, or integration issues. Check the link setup and parameters, and share examples with support for troubleshooting if the issue persists.

2. Why are payment methods (Apple Pay, Google Pay, Zip, etc.) missing?

Payment methods depend on your account configuration and enablement status. If expected options are missing, they may not yet be activated for your account or environment. Contact your account manager to confirm which methods are enabled.

3. Why are payments being declined even when details look correct?

Declines can occur due to issuer decisions, risk checks, or configuration issues. Review the error codes and logs returned with the transaction. If declines appear unexpected, contact support with the transaction reference for further investigation.

Tip: Always capture and log the full error response from the API — this is the fastest way to diagnose payment issues.

4. Can we support partial or split payments?

Yes, depending on your integration setup. Mint can support partial payments or multiple payment methods per transaction. This may require configuration changes — reach out to your account manager to discuss.

Tokenisation & Advanced Features

1. How does tokenisation or OTT (One-Time Token) work?

Mint supports tokenisation for securely storing and reusing payment details. You can request OTT keys, retrieve tokenised cards, and configure token behaviour via the API. Refer to the tokenisation section of our API documentation for implementation details.

2. Can we enable or change 3D Secure (3DS) settings?

Yes. 3DS2 can be enabled, disabled, or configured depending on your use case. This includes handling authentication flows and timing considerations. Contact support to adjust your 3DS settings.

Reconciliation & Data Issues

1. Why does Mint show a successful payment but our system shows an error?

This usually indicates a disconnect between Mint and your partner system (e.g. Tramada, PowerSuite). The issue may relate to callbacks, field mapping, or reconciliation logic. Review your webhook/callback configuration and contact support with specific transaction references.

2. Why are booking references or statement descriptors missing or incorrect?

This can happen if fields are not passed correctly in the API request, or if they are overridden by default settings. Review your integration payload and mapping configuration to ensure all required fields are included.

3. Can we customise payment metadata or returned fields?

Yes. Fields such as booking references, passenger names, and transaction notes can often be configured or passed through the integration. Speak with your account manager about your specific requirements.

Card Types & Configuration

1. Can we enable, disable, or change AMEX processing?

Yes. Mint supports different AMEX configurations (e.g. direct AMEX). Changes can be made based on your merchant setup. Contact your account manager to discuss your requirements.

2. How do surcharges and fees work, and can they be adjusted?

Surcharging rules depend on your configuration and integration (e.g. Tramada-specific behaviour). Mint can help adjust how fees are applied across different payment types. Reach out to support or your account manager for changes.

Troubleshooting & Stability

1. Why did our integration stop working when it was previously fine?

This could be due to expired credentials, configuration changes, partner system updates, or environment issues. Start by reviewing recent changes and checking your API logs. If the issue persists, contact support with details of when the problem began and any relevant error messages.

Tip: Set up monitoring on your webhook endpoints and API calls so you can detect issues early, before they impact your operations.

Still Need Help?

If your question isn't covered above, or if you need further assistance, we're here to help:

Contact your Account Manager for configuration changes, enablement requests, or onboarding support.
Reach out to Support for technical issues, debugging, or urgent troubleshooting.
Visit our API Documentation for detailed technical references and guides.