Transaction delivery success and failure

This document will show you how a Transaction can be marked as "Delivered" or "Failed", grouped by the type of Communication Channel.

HTTP

Transaction Delivered

• HTTP 2xx response (other than 202).
• HTTP 202 response + Delivery confirmation sent to the /approve endpoint.

Transaction Failed

• HTTP 202 response + Delivery confirmation sent to the /fail endpoint.
• The following responses will result in a retry: HTTP 404, 408, 409, 423, 429, 502, 503 or 504. After 3 unsuccessful retries we will mark the Transaction as "Failed".
• Any HTTP response not listed above will immediately result in a failed Transaction.

---

Poller

Transaction Delivered

• Confirmation sent to the /approve endpoint.

Transaction Failed

• Confirmation sent to the /fail endpoint.

---

AS2

Transaction Delivered

• Positive MDN received

Transaction Failed

• The following responses will result in a retry: HTTP 404, 408, 409, 423, 429, 502, 503 or 504. After 3 unsuccessful retries we will mark the Transaction as "Failed".
• Negative MDN received

For more information see AS2 Troubleshooting.

---

SFTP (Orderful Hosted)

Transaction Delivered

• File was deleted from SFTP server

Transaction Failed

• N/A

---

SFTP (Self Hosted)

Transaction Delivered

• File was uploaded to SFTP server

Transaction Failed

• File wasn't uploaded to SFTP server

---

VAN

Transaction Delivered

• Positive MDN received from Orderful VAN provider

Transaction Failed

• Negative MDN received from Orderful VAN provider