Payments2Us allows you to import bank account details and create AU BECS Direct Debit mandates in Stripe. While this provides flexibility, it’s crucial to understand Stripe’s compliance requirements when handling Direct Debit Requests (DDRs).
Mandate Collection & Customer Authorization
- When using offline mandates (imported bank account details), you must ensure customers have accepted the Direct Debit Request (DDR). This agreement need to be sent and signed by the customer/donor beforehand.
- The DDR must contain authorization text and include Stripe’s Direct Debit Service Agreement (DDR SA). Authorization text from the article linked in this point is:
- By providing your bank account details and confirming this payment, you agree to this Direct Debit Request and the Direct Debit Request service agreement, and authorise Stripe Payments Australia Pty Ltd ACN 160 180 343 Direct Debit User ID number 507156 (“Stripe”) to debit your account through the Bulk Electronic Clearing System (BECS) on behalf of (the “Merchant”) for any amounts separately communicated to you by the Merchant. You certify that you’re either an account holder or an authorised signatory on the account listed above.
Customer Notification for Mandate Migration
If you’re migrating existing Direct Debit mandates to Stripe, you must:
- Notify customers at least 14 days before processing the first payment.
- Share Stripe’s DDR Service Agreement with them.
Storing Mandate URL's
A new field Offline Mandate URL (AAkPay__Offline_Mandate_URL__c) is introduced in the recurring payment object. This field will store the customer's mandate URL fetched from Stripe. Stripe is expecting that this URL is stored in the system so that it can be provided if a customer requests proof of authorization.
You can also notify the customer/donor by sending them this mandate document before charging them. If you'd like assistance for automating this notification, then you will need one of our premium support packages to assist