Access PaySuite DDCMS sends a set of standard fields into Zapier whenever a customer, Direct Debit, payment or rolling payment event is used as a trigger. These fields are what you map into later steps in your Zap, and the exact fields available depend on the event and the data in your sample.
Trigger fields
Access PaySuite DDCMS triggers return essential information about customers, Direct Debits, payments, and rolling payments. Depending on your sample record, you may see:
CustomerReference, Name, Email and other customer details
Direct Debit information such as DDReference, Amount, Frequency and StartDate
Payment fields like PaymentReference, CollectionDate and Status
Rolling payment values including RollingPaymentID, InitialAmount and RecurringAmount
📌Note: Zapier only displays fields included in the sample. If something is missing, create a new test record in Access PaySuite DDCMS and reload the trigger.
Action fields
When sending information into Access PaySuite DDCMS, required fields depend on the action:
Creating or updating a customer requires CustomerReference
Creating a Direct Debit requires CustomerReference, StartDate, Amount and Frequency
Updating a Direct Debit requires CustomerReference, DDReference, plus the field you’re updating
Creating a payment requires CustomerReference, Amount and PaymentDate
Static text can be combined with mapped fields where useful, for example:
DD-{{CustomerReference}}.
Format requirements
For successful validation:
Dates must use YYYY‑MM‑DD
Amounts must be numbers only
Frequency values must be Weekly, Monthly, or Annual
📌Note: Custom fields created in Access PaySuite DDCMS are not available in Zapier.
Common issues
Missing required fields: ensure all mandatory fields are mapped
Invalid date or amount formats: dates must use YYYY‑MM‑DD, amounts must be plain numbers
Unrecognised references: confirm both steps use the same environment (Sandbox or Production)
Empty trigger values: create a fresh test record and reload the sample