What is the reassessment? A course? Or, an activity within a course where they already took the course and then took the assessment, but there is a fee to take the assessment again?
If it were me, I would create a course with one activity, just the reassessment. (Maybe the assessment is in a course with other activities as well, but there doesn't need to be a gateway for that one.)
You'll have to share more. But, the idea of a separate course would separate the users who need reassessment from those who did not, and you could make the gateway for just that course, specific to the reassessment. Like
Howard was saying, if you want the payment to go with enrollment into that course.
But you are describing a manual process of "seeing if they paid" through the mechanism of somehow what your "gateway" produces to you, and then you "let them in" or enroll them, or whatever.
Key question: are you trying to automate enrollment with a payment, or simply figure out how to get yourself a usable response from your gateway code and then manually go from there? Because custom code may be needed
for either option. However, if you are automating there is more involved though it could be started with existing code for automatic enrollment through existing plugins, etc. If you're going manual in the enrollment process, it is simpler and you may just
need to work out how you want the PayTabs response to get to the user who reviews student payments, etc.
Please share your decision regarding which direction you are trying to go.
(Edited by Howard Miller to remove quoted text- original submission Tuesday, 22 January 2019, 11:50 PM)