The test and production hosts, and how to test before you go live.
Master: api-docs.aerahost.comWe're moving our API docs to docs.aera.id. Until the move is done, 2.1. Access to the APIs, 2.1.1. Configuration tips and 2.2.1. HTTP Request URL on api-docs.aerahost.com are the master for this page. If this page and api-docs differ, api-docs is right.
Aera has two environments. Build and test in test (also called PreProd or customer test). It works like production, but no real money moves.
| Environment | Online payments (PSP) | Reporting API and other services |
|---|---|---|
| Test | https://psp-staging.aerahost.com | https://api-staging.aerahost.com |
| Production | https://psp.aerahost.com | https://api.aerahost.com |
Every request goes to https://<host>/<path>, for example https://psp-staging.aerahost.com/access/v1/oauth2/token. Use HTTPS for every request. Test and production have separate credentials. See Get access.
Test your integration
| API | How to test |
|---|---|
| Online payments | Use the test host and your test credentials |
| Reporting API | Use the test host and your test credentials. Your webhook URL receives test reports |
| Terminal messages (Nexo) | Use an Aera test terminal, test cards and the ECR simulator. See Get your test kit and Set up your test environment |
Never use real cards in test, and never use test cards in production.
Keep the host address up to date
The IP addresses behind Aera's hosts change from time to time. Make sure your system looks up the address again at least every 60 seconds (a DNS cache time of 60 seconds or less). Otherwise your requests can fail after a change.
Java: set the DNS cache time
Java can keep an old address until the application restarts. Set the cache time to 60 seconds, either in the java.security file:
networkaddress.cache.ttl=60or when your application starts:
java.security.Security.setProperty("networkaddress.cache.ttl", "60");Go live
When your integration works in test, ask for production credentials. See Get access.