PayTo Notifications

Shaype receives notifications from the MMS for any action made to a PayTo agreement for which the client is the Payment Initiator. Examples of MMS notifications are: 

  • PayTo agreement authorisation responses (accepted, declined, expired) 
  • PayTo agreement status changes made by the Debtor (suspended, released, cancelled). 

It is up to the client as to if/how they present PayTo Notifications to their customers, including: 

  • How the amended data is made available to the customer, and 
  • If the customer is informed of mandate suspension/unsuspension, and cancellation by the Debtor 

Notifications may be presented to your customers via SMS, email or in-app push notifications.

Notifications on Payer Actions

MMS CodeNotification RecipientNotification Name
MAMCInitiatorMandate Amend Confirmed
MAMDInitiatorMandate Amend Declined
MAMNInitiatorMandate Amended
MCRCInitiatorMandate Create Confirmed
MCRDInitiatorMandate Create Declined
MCRRInitiatorMandate Create Recalled
MSCHPayer & InitiatorMandate Status Changed
MCRTPayerMandate Requires Authorisation
MAMPPayerMandate Amend Proposed

Notifications on MMS Actions

MMS TriggerNotification RecipientNotification NameRemarks
MAMXPayer and InitiatorMandateAmendExpiredExpiry will be determined by MMS. Sent to the performer of an amend action once its expiry time has been reached and the status of the action is set to Timed Out (TIMO). For a bilateral amend action, this notification is also sent to the servicer of the Debtor Account.
MCRXPayer and InitiatorMandateCreateExpiredExpiry will be determined by MMS

Notifications on PayTo Payments

  • The Mandate Payment Event notification includes payment instruction ID, Mandate ID and final status.
  • It is sent for all payment instructions when the final status is known
  • After triggering the payment initiation the client can check the Get Payment instruction status by Mandate ID and Payment Instruction ID endpoint if the final status notification is not received.