#phal0r - Mobile payment sheet, setup intents for sepa and sofort

1 messages · Page 1 of 1 (latest)

quick stirrupBOT
carmine ridge
#

Hello

#

Can you give me a SetupIntent ID that you tested with while I look further?

naive mesa
#

sure, one second

#

here we go: seti_1Lsa1eBedPgr0Zv21KATHtr1

carmine ridge
split rose
#

Yes that sounds right ☝️

naive mesa
#

screenshots and code comments suggest, that it should work. So these are copy/paste errors?

split rose
#

Which code comments in particular are you referring to?

naive mesa
#

In step 3 it says in the code:

// Set `allowsDelayedPaymentMethods` to true if your business can handle payment
      // methods that complete payment after a delay, like SEPA Debit and Sofort.
      configuration.allowsDelayedPaymentMethods = true
#

and further below in step 3, there is a big grey info box, explaining allowsDelayedPaymentMethods and how payment is delayed for these methods

split rose
naive mesa
#

yeah, we checked this table aswell

#

So it's only a limitation of the native SDKs?

split rose
#

That seems to be the latest update regarding those payment methods, but I'm looking for more info

#

phal0r - Mobile payment sheet, setup intents for sepa and sofort

naive mesa
#

ok, thx

#

If it is not possible via PaymentSheet, what is the intended way to collect payment data for iban, sofort and other delayed methods in a mobile app. I would appreciate any hints into this direction.

split rose
#

Yea as far as i can tell that a limitation of current payment sheet support

naive mesa
#

ok, if I understand correctly, it is only possible with the javascript sdk

#

Is this correct?

split rose
#

Hmm the sofort docs do include IOS specific guides, so you can review that

#

I'm looking again for sepa, that seems unexpected

naive mesa
#

true, but it works different. The "normal" in my understanding is to create the SetupIntent with the off_session mode, so we can trigger payments server side, which is necessary for our business case.

In step 6 of the sofort guide, one should take the payment method id from the last SetupIntent. Also SetupIntent is not created with off_session mode. So I am not sure, if it allows the same kind of usage.

split rose
#

While the sofort setup intent example does not use off session, you can set that for your use case

naive mesa
#

like initially described, we create the SetupIntent like so:

...
"payment_method_types": [
      "card",
      "sepa_debit",
      "sofort"
    ],
"usage": "off_session"
...
#

but neither sofort nor sepa show up in the PaymentSheet

split rose
#

Correct, payment sheet does not currently support setup intents for those. You'd need to collect them separately.

naive mesa
#

ah, yeah

split rose
naive mesa
#

this is what the guides suggests, sorry

split rose
#

Edited above to be more precise, it doesnt support setup intents for those. You can use them for one time payment.

naive mesa
#

ok, so I can switch to the JS SDK to collect payment information and follow the according guides.

Now only the native PaymentSheet allows to trigger the scanning of credit cards with the ML model for detection. Can the scanning of credit cards be triggered separately without the PaymentSheet?

#

Since we develop a hybrid app I can use the JS SDK for the payment components and still have access to the native layer. So it would be cool if we would still be able to trigger this.

split rose
#

OK great -- for the card scanning bits I need ot step away but @rocky knot can give you a hand

old nebula
#

@naive mesa Did you still need help?

naive mesa
#

yeah, would like to get @rocky knot s opinion on my question, if the credit card scanner can be used without PaymentSheet

old nebula
#

Yes, I believe the Credit Card Scanner can be used with other components like the STPAddCardViewController, which is separate from the payment sheet

naive mesa
#

Is there any example, so I can check further?

old nebula
naive mesa
#

ok, thanks so far

#

if I have further questions, I will create a new thread