Accidental IBFT In (SP-SP)
Print
Created by: Eeman.shabbir
Modified on: Tue, 7 Oct, 2025 at 6:52 AM
This is a case when a SadaPay user initiates an IBFT Out transfer to another SadaPay user accidentally. In such scenarios, the recovery process is initiated to verify the transaction details, obtain user consent where required and coordinate the reversal in compliance with internal procedures. Here are the steps taken by CMU: CMU will send an OB message requesting recovery for the transaction that was accidentally sent to the SadaPay user from the ticket created by DRU. Ticket status will be changed to “Good Faith Recovery”. First Follow-Up: CMU conducts the initial follow-up with the user to inform them about the recovery request and confirm their acknowledgment. Second Follow-Up: If there is no response, CMU initiates a second follow-up 14 days after the first, serving as a reminder and requesting the necessary consent or information. Third Follow-Up: CMU conducts a third and final follow-up 14 days after the second, emphasizing the urgency and next steps required from the user. Closure: If the user does not respond within 14 days after the third follow-up, CMU closes the ticket and changes ticket status to ‘Done’ due to lack of user response.
User Agreement for Reversal (SP-SP): The CMU team will create both a MA debit and credit ticket simultaneously and link them. In the MA debit ticket, the CMU team will add information regarding the receiving account from which the debit should occur. In the MA credit ticket, the CMU team will mention the sender's account details for the refund.
|
Eeman is the author of this solution article.
Did you find it helpful?
Yes
No
Send feedback Sorry we couldn't be helpful. Help us improve this article with your feedback.