What’s the Difference Between Promissory Responses and Presentment Responses?

What is a Promissory Response?

A Promissory Response is a message from Allps telling your system that something has changed about a the mandate or promissory note). It represents changes in the agreement that authorizes payments — not the payments themselves.

Typical events:

• A new mandate is created

• An existing one is edited or updated

• One is recalled, suspended or cancelled

Promissory responses manage the setup and status of that permission to collect future instalments.

---

What is a Presentment Response?

A Presentment Response is a message about an actual debit attempt — when the system presents an instalment to the client’s bank for payment.

It shows the result of each attempt:

• Was the debit successful?

• Did it fail or get disputed?

• Was it recalled, suspended, or resubmitted?

Presentment responses manage the execution outcome of those bank transactions.

---

Core Differences

Promissory Response	Presentment Response
Mandate / Authorization	Instalment / Transaction
Tracks changes to the debit authority itself	Tracks the result of using that authority
Only when mandate is created, changed, or cancelled	Every payment cycle or debit attempt
Promissory record	Presentment record
Update mandate status, notify branch	Record collection result, create on‑hold / collection tasks
Active vs Cancelled vs Stopped mandates	Paid vs Failed vs Disputed debit orders

---

Why both are needed

You need both datasets to maintain a complete payment lifecycle:

1. Promissory: confirms you have permission to attempt a debit.

2. Presentment: records what actually happened when you exercised that permission.

Without promissory updates, you can’t tell if a client’s mandate is valid. Without presentment results, you can’t tell whether money was successfully collected.

---

Do both record cancelled or stopped actions?

Yes — both models capture “cancel” or “stop” events, but they represent different layers of the debit‑order process:

Layer	Data Model	What’s being stopped	Example Response Codes
Mandate / Setup	Promissory	The authorisation itself (the client’s consent to collect)	103 = Cancellation, 410 = Recall, 414 = Edit
Payment / Execution	Presentment	A specific debit attempt or instalment	510 = Dispute, 549 = ACOL Suspension, 573 = RMAN Suspension

In short: - Promissory “cancelled/stopped” = the permission to debit has ended. - Presentment “cancelled/stopped” = a specific payment attempt failed or was halted.

---

Response Type Codes and Meanings

Below are the numeric Allps response types your integration currently fetches, grouped by category.

Promissory Response Types

Code	Description	Typical Stage / Event
403	Promissory Note Activation	A mandate has been activated / accepted by the bank.
103	Promissory Note Cancellation	A mandate was cancelled (client, branch, or bank instruction).
408	Instalment Edit	Changes made to scheduled instalment values or dates.
410	Instalment Recall	A previously sent instalment is recalled from processing.
412	Promissory Note Edit (with Card)	Editing of card‑based mandate details.
414	Promissory Note Edit	Editing of EFT/NAEDO mandate details.
105	AEDO Promissory Note Creation	New AEDO mandate created.
107	NAEDO Promissory Note Creation	New NAEDO mandate created.
109	NAEDO Promissory Note Creation with Card	NAEDO mandate tied to card data.
117	EFT Promissory Note Creation	EFT mandate created (standard debit order).
119	EFT Promissory Note Creation with Card	Same as above, with card link.
131	Social Grant EFT Promissory Creation	EFT mandate for social‑grant account.
132	Social Grant EFT Creation with Card	Same, card‑linked.
133	EFT Same‑day Promissory Creation	Same‑day debit mandate.
134	EFT Same‑day Promissory Creation with Card	Same‑day debit mandate with card data.
140	ACOL Promissory Creation with Card	ACOL (authenticated collections) with card.
141	ACOL Promissory Creation	Standard ACOL mandate.
145	RMAN Mandate Creation	Mandate via RMAN platform.

Each one tells you how a client’s debit‑order authority was created or modified.

---

Presentment Response Types

Code	Description	Category
503	AEDO Presentment Result	Outcome of an AEDO debit attempt.
508	NAEDO Presentment Result	Outcome of a NAEDO debit attempt.
510	NAEDO Presentment Dispute	Dispute raised on NAEDO debit.
511	NAEDO Presentment Dispute After 40 Days	Late dispute on NAEDO.
533	EFT Dated Presentment Result	Regular EFT result.
534	EFT Same‑day Presentment Result	Immediate EFT collection result.
536	EFT Presentment Dispute	EFT transaction contested.
540	Grindrod EFT Presentment Result	Result for Grindrod channel.
541	Grindrod EFT Presentment Dispute	Dispute for Grindrod channel.
544	Social Grant EFT Presentment Result	Debit result for social‑grant EFTs.
545	Social Grant EFT Presentment Dispute	Dispute on social‑grant EFTs.
546	ACOL Presentment Result	ACOL debit outcome.
547	ACOL Tracking	Tracking progress on an ACOL debit.
548	ACOL Presentment Dispute	Dispute on ACOL debit.
549	ACOL Mandate Suspension	ACOL debit temporarily stopped.
550	ACOL Bank Error	ACOL banking error response.
555	ACOL Creation Authentication	Authentication message for ACOL creation.
556	ACOL Edit Authentication	Authentication for ACOL change.
557	ACOL Cancellation Authentication	Authentication for ACOL cancellation.
570	RMAN Presentment Result	RMAN debit result.
571	RMAN Tracking	RMAN debit tracking update.
572	RMAN Presentment Dispute	RMAN dispute.
573	RMAN Mandate Suspension	RMAN suspension event.
574	RMAN Bank Error	RMAN bank error.
575–577	RMAN Creation/Edit/Cancellation Registration	Administrative confirmations.
240–251	POS Settlement / Refund Events	Card or point‑of‑sale debit/credit settlements.

These codes cover every scenario where the system actually tried to collect, recorded an outcome, or handled a dispute/refund/suspension.

---

In short

Promissory Responses look after the permission and setup for debit orders. Presentment Responses record the money movement and results of each debit attempt.

Both are vital:

• Promissory = compliance and authorization record.

• Presentment = cash‑flow and collection tracking record.