MGRNET · AS2 fact sheet
Connection details for the partner · 22/10/2026
MGRNET · AS2 fact sheet
Connection details for the partner · 22/10/2026
| Configuration data | |
|---|---|
| URL — HTTPS TLS 1.2 or higher | https://as2.mgrnet.com.br/as2/as2receive/ |
| MGR's AS2 ID use as AS2-To when sending | MGRNET |
| MDN | Synchronous / Asynchronous |
| Signed MDN this is what provides proof of delivery | YES (recommended) / NO |
| MDN transport | HTTPS |
| Signature algorithm | SHA-256 (default) / SHA-384 / SHA-512 / SHA-1 (legacy) |
| Encryption algorithm | AES-256-CBC (default) / AES-192-CBC / AES-128-CBC / 3DES (legacy) |
| Compression | Supported (optional) · up to 32 MiB per message |
| Accepted content types | application/EDIFACT · application/edi-x12 · application/edi-consent · application/XML · application/octet-stream |
| Ports | HTTPS: 443 there is no plain-HTTP endpoint |
| Inbound IP | No fixed IP the endpoint sits behind the Google Cloud edge — allow it by host name, not by IP |
| Outbound IP | No fixed IP outbound through Google Cloud (southamerica-east1), dynamic range. If your policy requires IP allow-listing, talk to MGR before the acceptance tests. |
| Signing / encryption certificate | https://as2.mgrnet.com.br/as2/organizacao/MGRNET/certificado/ same file with a .cer extension: https://as2.mgrnet.com.br/as2/organizacao/MGRNET/certificado/?formato=cer |
| Published certificate | |
|---|---|
| Subject | 1.2.840.113549.1.9.1=diretoria@mgr.com.br,CN=b2b.mgrnet.com.br,OU=EDI,O=MGR e-technologies,L=Rua Silva Bueno\, 1660 - sala 608,ST=Sao Paulo,C=BR,2.5.4.5=O0055MGROFTP2 |
| Validity | 23/04/2026 → 23/05/2030 |
| Serial number | 3800001C390A6B7B8D07EF4B0A000000001C39 |
| Fingerprint (SHA-256) check it after downloading | 84:A5:7C:53:9F:2B:FD:D0:D2:D7:6F:28:77:D8:04:57:7D:C3:34:DE:9F:95:AD:15:1A:35:08:BA:D9:4A:37:6A |
| Key | RSA 2048 bits |
| Notes | |
|---|---|
|
The AS2 ID is case-sensitive and must match byte for byte on both sides. A mismatch here shows up as an unknown partner or an authentication failure. MGR accepts signed and encrypted messages and requests a signed MDN by default. If your server does not sign the MDN, let us know before the acceptance tests so we can adjust the configuration. For an asynchronous MDN, provide the return URL on your side — without it the receipt has nowhere to go back to. Check the fingerprint above after downloading the certificate. It is what tells the genuine file apart from one swapped along the way. |
| Certificate renewal | |
|---|---|
|
MGR's certificate expires on 23/05/2030. MGR's AS2 server does not implement CEM (Certificate Exchange Messaging, RFC 6362): certificates are exchanged by prior arrangement, not automatically. We get in touch one month before the expiry date to arrange the replacement. The same applies the other way around: let us know just as early when your certificate is about to expire. For this to work, keep a valid technical e-mail address on file with MGR. |
| Contact | |
|---|---|
| Company | MGR e-Technologies |
| AS2 support |
suporte@mgr.com.br +55 (11) 2065-1744 |
| Addresses | |
|---|---|
| MGR website | https://www.mgr.com.br |
| AS2 portal the system that receives and sends the messages | https://as2.mgrnet.com.br |
| This sheet, always up to date the data comes from the live configuration — reprint it rather than filing it away | https://as2.mgrnet.com.br/en/ficha-as2/ |
| Implementation guide | https://as2.mgrnet.com.br/en/guia-implementacao/ |