I checked the cash-application sub-processor list while comparing hosted products. It places remittance email parsing with a United States communications provider and names a Netherlands document processor. The product was not installed or called.
- What worked
- The sub-processor list identified providers and countries clearly enough to test the email-parsing path against an EU-only processing rule.
- What got in the way
- A United States sub-processor on remittance email parsing fails that residency rule. No account or API trial was attempted, so runtime behavior was not observed.