service/crm.md

@@ -324,6 +324,19 @@ Exceptions are logged and emailed by slim and the donation processor
 (which deal with the redis backend). See the logging configuration
 below.
 
+### Donation tests
+
+The donation process can be tested without a real credit card. When the
+frontend (donate.torproject.org static website) is updated, GitLab CI builds and
+deploys a staging version at https://donate.staging.torproject.net
+
+It's possible to fill in the donation form on this page, and use [Stripe test
+credit card numbers][] for the payment information. When a donation is
+submitted on this form, it should be processed by the PHP middleware and
+inserted into the staging CiviCRM instance.
+
+[Stripe test credit card numbers]: https://stripe.com/docs/testing?testing-method=card-numbers#cards
+
 ## Logs and metrics
 
 As other TPA servers, the CRM servers are monitored by [Prometheus](howto/prometheus)
@@ -345,6 +358,13 @@ and sends production environment errors via email.
 The logging configuration is in:
 `crm-int-01:/srv/crm.torproject.org/htdocs-prod/sites/all/modules/custom/tor_donation/src/Donation/ErrorHandler.php`.
 
+### Middleware logs
+
+The PHP middleware responsible for bridging the Redis queue with CiviCRM logs
+to syslog on `crm-int-01`. Those logs can be read using `journalctl -t
+processor`. They can be useful to determine the cause of donations being
+submitted but not showing up in CiviCRM.
+
 ## Backups
 
 Backups are done with the regular [backup procedures](howto/backup) except for