eMandates do not contain any reference fields. NPCI does not permit them. Rather, NPCI requires that participants should capture the ONMAGS Reference ID when the customer authorises an eMandate. Participants should store this value and use it for reconciliation. If you want to store your custom identifier with an eMandate, you may use LotusPay metadata.
Physical mandates contain two reference fields. You can use these fields to store your custom identifiers in the mandate. These will help you to do reconciliation later, and will also help your customer to identify the purpose of the mandate in case they view it. The maximum length is 40 characters, and you may include alphabet and number characters.
Reference 1 (sometimes referred to as Customer Reference) is mandatory. It an be used to store your product/service/customer reference. If you do not give a value, LotusPay will automatically insert the Mandate ID into Reference 1.
Reference 2 (sometimes referred to as Plan/Scheme Reference) is optional. It can be used to store an additional identifier.
LotusPay provides metadata fields in all resources, including eMandates and physical mandates. Metadata allows you to store your custom identifiers in key-value pairs in the object.