Environment Configuration

[!INFO] Two Environments

a55 provides two environments: Sandbox for development and testing, and Production for live transactions. Both use the same API structure but require different credentials.

Environment Comparison

flowchart LR
    subgraph sandbox [Sandbox]
        S1[Test Mode]
        S2[Test Cards]
        S3[No Real Money]
    end
    
    subgraph production [Production]
        P1[Live Transactions]
        P2[Real Cards]
        P3[Settlement]
    end
    
    sandbox -.->|After Testing| production

API Endpoints

Environment	Base URL	Auth URL
Sandbox	`https://core-manager.a55.tech/api/v1`	`https://smart-capital.auth.us-east-1.amazoncognito.com/oauth2/token`
Production	`https://core-manager.a55.tech/api/v1`	`https://smart-capital.auth.us-east-1.amazoncognito.com/oauth2/token`

[!WARNING] Same endpoints, different credentials
While the URLs are identical, you'll receive separate client_id and client_secret for each environment.

Sandbox Environment

The sandbox is your development playground:

Feature	Description
🧪 Test Mode	All transactions are simulated
💳 Test Cards	Use special test card numbers
🚫 No Real Money	No financial impact
🔄 Unlimited Testing	Test as many scenarios as needed

Sandbox Credentials

Your sandbox credentials will be provided during onboarding:

# Environment Variables (example)
export A55_CLIENT_ID="sandbox-xxxx-xxxx-xxxx"
export A55_CLIENT_SECRET="sandbox-secret-xxxx"
export A55_ENV="sandbox"

Production Environment

The production environment handles real transactions:

Feature	Description
🚀 Live Transactions	Real money, real cards
🔐 KYC Required	Full onboarding and compliance
💰 Settlement	Funds transfer to your accounts
📈 Analytics	Full reporting dashboard

Production Credentials

Production credentials are issued after completing onboarding:

# Environment Variables (example)
export A55_CLIENT_ID="prod-xxxx-xxxx-xxxx"
export A55_CLIENT_SECRET="prod-secret-xxxx"
export A55_ENV="production"

[!DANGER] Never mix environments Never use production credentials in staging or development. This could result in real charges to real cards.

Best Practices

Practice	Description
🔒 Secure Storage	Use environment variables or secrets manager
🚫 No Hardcoding	Never commit credentials to version control
🧪 Test First	Complete sandbox testing before production
🔑 Rotate Regularly	Rotate secrets periodically
📝 Log Safely	Never log credentials or full tokens

Request Credentials

[!TIP] Contact Our Team To request credentials for either environment, email [email protected] with:

Company Name & CNPJ

Contact Email

Environment needed (Sandbox / Production)

Brief use case description

Next Steps

Test Cards — Get test card numbers for sandbox
Integration Overview — Choose your integration method