#Sven

1 messages · Page 1 of 1 (latest)

buoyant hingeBOT
terse panther
#

Hi
I'm not sure I understand what you mean exactly by "generate ourselves a mandate reference (ID)" ?

visual thicket
#

We are using a fully server side approach. We collect mandates ourselves and just send the charge (paymentintent create) request to Stripe to actually execute the payment.

#

For example, our test live payment: pi_3NG0BKKykkNsEbHP2f3SHorm

#

Everything went well. But the mandate reference was generated by stripe, not provided by us:
“ […] , with mandate reference WWEAE5JAZLXMG3EO and creditor identifier […]”

#

The email must include:
The last 4 digits of the debtor’s bank account
The mandate reference (sepa_debit[reference] on the Mandate)
The amount to be debited
Your SEPA creditor identifier
Your contact information

#

However we would like to submit a mandate reference we generated, rather than one dynamically generated by Stripe. So we would need to supply a reference during the API call when creating the paymentintent

#

But I do not seem to find a field for it within the docs

terse panther
visual thicket
#

If we use 2 PSP’s that would be confusing if every PSP has their own mandate reference. Especially if we indicate our own on our invoices

terse panther
visual thicket
#

I see. Is there any way to have this feature added in the future, to be able to provide mandate references?

terse panther
#

Not something in track currently, AFAIK.

visual thicket
#

It seems that Mandates (instead of PaymentIntent) supports this actually:

payment_method_details.sepa_debit.reference
string
The unique reference of the mandate.

#

Sorry, that’s just the standard Mandat object, not the actual create request

visual thicket
terse panther
terse panther
visual thicket