- Use the HTTP/REST endpoints
- Take advantage of our SDKs
- Make use of our official integrations
Environments
Mangopay provides two environments:| Production | Sandbox |
|---|---|
| https://api.mangopay.com | https://api.sandbox.mangopay.com |
Note – Proxy management for SCA requires mTLS base URLIf your platform is using proxy management to take SCA-triggering actions on behalf of users, you need to use mTLS authentication.This integration requires a different base URL, with
api-mtls in the hostname. The mTLS base URL should be used for all API calls, including OAuth token generation.If you are not using proxy management, you need to use the base URLs shown above.| Content-Type | application/json |
|---|---|
| Encoding | UTF-8 JSON |
Note – Endpoints requiring a different Content-TypeThere are two endpoints that require the application/x-www-form-urlencoded Content-Type:
- The OAuth token endpoint – see OAuth 2.0 authentication
- The Tokenize the card endpoint, which is a URL returned by the API
UK platforms
Previously, Mangopay required platforms that contracted with Mangopay’s UK entity to include an HTTP header in all API requests in Production. This is no longer the case. The headerx-tenant-id (with values eu (default) or uk) is deprecated and ignored by Mangopay if sent.
In the SDKs, there was a UK header flag boolean which, when true, set the header value to uk.
The tenant notion was replaced with the Licensor field of the API’s Client object, and it is set automatically by Mangopay.