Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Payment Plugins

    (@mrclayton)

    Hi @dsturm

    You linked to Stripe’s deprecated Source API which is not used by this plugin. There isn’t a way to disable the capture of address info. If the address field doesn’t exist, the value will just be blank which will suffice.

    Please note that SEPA does require customer name, email, country, and in many countries the line1 property of the address. I wouldn’t suggest removing your billing address fields from the checkout page.

    https://docs.stripe.com/payments/sepa-debit/accept-a-payment?web-or-mobile=web&payments-ui-type=elements

    Kind Regards

    Thread Starter Daniel Sturm

    (@dsturm)

    Hi @mrclayton,

    thanks for your answer and clarification towards the linked docs / API.

    The official Stripe plugin only asks for IBAN in the payment process – which seems more convenient to me – and uses billing data for the source object without showing inputs to the customer.

    Since WC_Payment_Gateway_Stripe_Local_Payment::get_source_owner_args() also fills out the address array with the order specific data, isn’t there a way to rely only on this data?

    Kind regards,
    Daniel

    Plugin Author Payment Plugins

    (@mrclayton)

    Hi @dsturm

    The official Stripe plugin only asks for?IBAN?in the payment process

    Just because another plugin does something that doesn’t mean it’s correct or the right way.

    and uses billing data for the source object without showing inputs to the customer.

    It’s impossible to use billing data that doesn’t exist. Billing data comes from user provided inputs.

    isn’t there a way to rely only on this data?

    That’s a deprecated method that was used as part of the old Sources API. In addition, you will notice that all the address info from that method comes from the WC_Order. The WC_Order gets it’s address info from the checkout page billing address fields.

    Kind Regards

    Thread Starter Daniel Sturm

    (@dsturm)

    Hi @mrclayton,

    thanks again for your answer – I don’t know why, I didn’t receive a notice about this although I did opt in. ??

    Sure, just because another plugin does something doesn’t mean it’s correct. On the other hand, I assumed that this was the “official” way.

    However, I think there is a different problem for me: I’m using the PRO version of Germanized for WooCommerce, where I’ve enabled a delayed conclusion of contract. At the time of payment it looks like the billing address data of the order isn’t used (or available) for the payment form. So, currently the customer has to fill out every input. That’s why it seems to be slightly frustrating for a customer.

    If I have understood you correctly, all the corresponding address fields should already be pre-filled. Correct? So, it looks like your plugin relies on inputs from the checkout – and I think while paying for a delayed contract at the pay_for_order endpoint these inputs are lacking.

    I will try to narrow down this problem further.

    Thanks again,
    Daniel

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.