Stripe ACH - data
When a Stripe ACH payment is submitted by a supporter, you will see two FBR transactions created over time. These are:
A transaction for the supporter submitting the payment, which will initially have a status of “Pending” until Stripe confirm whether it was successful
This is followed later by a “change” transaction, which details the change of status from “pending” to “success” or “reject” once Stripe confirms
We’ll detail them all here by using some examples.
Example data
In the explanation, we’ve abbreviated “Campaign Data” to “CD” for clarity.
Row 1: Column headings. We’ve selected the most important columns for this explanation. All of them will have a Campaign Type of “FBR”
Row 2: Initial payment. Here the supporter made an ACH for $10 a month, on the 24th November (first row), with a Recurring Day of 1 (CD 8).
Because of this, the API (which uses staged data) will still always show a “pending” status here, but live exports (from the query builder) will eventually show the updated status
Row 3: Payment request status change: This shows that the status was changed from “pending” to “success”. You can see that the ID (CD1) is the same as the previous transaction since this change relates to that transaction.
Supporter ID | Campaign date | Campaign Status | Campaign Data 1 | Campaign Data 4 | Campaign Data 8 | Campaign Data 21 | Campaign Data 22 |
250709073 | 2024-11-24 | pending | pm_xxx__cus_yyy__mandate_mmm | 10 | 1 |
|
|
250709073 | 2024-12-01 | change[] | pm_xxx__cus_yyy__pi_aaa | 10 | 1 | pending | success |
What does a payment look like in Stripe?
Metadata
Each payment made in Engaging Networks and passed to Stripe will have Stripe’s metadata stored with it. These are pieces of information about the payment that you can set:
pagename - the name of the page
provider - always engagingnetworks
taxdeductible - for Gift Aid in the UK, this is either Y or N
appeal code
other1, other2, other3, and other4