To try and locate the cause of this, please check the following.
- Check error logs. First check against the import file line item to see if there is an error reported. If not, go to the Error Log tab and look at Errors created for today.
This is the most likely area to have the reason for the error. It could be that a validation rule or a process builder that has been added to your instance is causing the issue and the error log will contain a description of the issue. - Check on Import File Line Item and Payment Txn. Are there any fields with the same API name. E.g. AAkpay__receipt_number__c is the same as receipt_number__c. Please check all custom fields that have been added. It might be that we've added a field with the same name to a future release and that is why it is now causing an issue. Rename the custom field with a duplicate name.
- Navigate to Setup. Search "Apex Jobs". Locate the importprocessor jobs. Does an error show here?
- Make sure you are on the latest release of Payments2Us