Integration Guides

Business Rules

Suggest Edits
  1. If a Register or Update request is sent and the card/accountNumber is already linked to the same MSISDN a “CARD LINKED TO PROFILE” result will be returned.
  2. If a Register or Update request is sent and the card/accountNumber is linked to a different MSISDN then an “ALREADY LINKED” result will be returned.
  3. Delink, Block and Unblock requests will only return a “SUCCESS” if the card/accountNumber and MSISDN match up to the customer’s wallet/app profile that is reflected on the system.
  4. On the Update request the expiryDate, imageId or cardholderName must be supplied on the request.
  5. On Update if the card/accountNumber is in a “BLOCKED” status a “SUCCESS” will be returned but the card/accountNumber will remain in a “BLOCKED” status.
  6. On Update if the card/accountNumber is “DELINKED” a “CARD DELINKED” status will be returned.
  7. On Update the user will not be able to specify node, validation method or state; this functionality is only available on the Register function.
  8. If the node being used on the Register request does not exist this will be dynamically created on the MRA backend and the accountnumber/PAN will be assigned to that node. Please make sure with the Scan to Pay service provider on the node to be used when registering an accountNumber/PAN to a wallet.
  9. If no state is stipulated on Register the accountNumber/PAN will be hard linked to the MSISDN and no other MSISDN will be able to use it thereafter.
  10. If the validation method is not stipulated on Register the accountNumber/PAN will merely appear in the customer’s wallet.
  11. If the accountNumber/PAN requires an account type, the account parameter must be specified on the request; the account type will default to credit if the invalid account has been sent. I.e. not 10, 20 or 30.

Updated about 2 years ago