#birdbill-cloned-payments

1 messages · Page 1 of 1 (latest)

sleek quest
#

Can you attach the payment method to an existing customer before creating the PI?

white willow
#

"payment_intent": "pi_3KxgoWLTgirc5WaA01JHwm60",
"payment_method": "pm_1KxgoWLTgirc5WaAWPbi0xvh"

sleek quest
#

If you get the customer's email via billing_details on the PM, it should default to using the same customer object for all payments with that email. Otherwise I would recommend creating a customer and attaching the payment method. There's no way to stop guest accounts from being created otherwise, as far as I know.

white willow
#

ok thanks. our customers and pay methods are on the platform before the transaction (pi) is created. so i guess it's unavoidable. would it be fair to submit a feature request to suppress our platform customer info from creating these? i suppose the connected acct view will still allow the customer to see 👀 the customer details though...

#

when using a wallet like apple pay, those data arent necessarily shared so the customer may remain "anonymous" to the connected acct