Datacapt tracks what you owe your participants and gets it ready for your bank. It does not move the money. This article defines the words the payment articles use, and sets out what the module does and does not do.
⚠️ Warning: Datacapt does not process payments. It tracks, validates and exports a structured list of payment records; the actual transfer happens in your own banking system. A payment marked as paid in Datacapt tells you somebody recorded it as paid, not that your bank has sent anything.
What the words mean
Payment order: a payment record attached to one participant under one recruitment study.
Payment type: when the order is generated. Either at the end of the study (Per Study) or after each visit (Per Visit).
Payment amount: the monetary value on the payment order.
Payment status: where the order has reached in the Datacapt workflow. It tracks the order inside Datacapt only, and is not connected to the bank transfer.
Payment Order management: a global dashboard that sits outside individual recruitment studies. It brings every payment record together so your finance team can review, validate and export them in one place.
What the module depends on
A payment record is always attached to a recruitment study and cannot exist without one. If payment orders are not appearing, the recruitment study setup is the first place to look, not the payment module.
Getting the data out
There are three ways to hand payment data to whoever pays:
A structured ISO Bank SEPA file, for payments inside the EU.
A structured CSV document.
A direct integration with your own systems, through the Datacapt API.