#dafrancofl-paymentintents

1 messages · Page 1 of 1 (latest)

boreal timberBOT
supple folio
#

You can do that

#

But you should still use payment intents instead of charges

#

Charges are our old api

boreal timberBOT
#

dafrancofl-paymentintents

bright peak
#

So sorry but I'm not gettting it. The final state would be using both setup intents and payment intents together. But would be better for us using setupIntents + charges API for some time, isn't that possible?

supple folio
#

It's possible yeah

#

But charges don't support 3ds, etc

#

Recommend you use payment intents

#

What you want is possible, but we won't recommend you do that

bright peak
#

Got it, yes we know about the risks, we'd use that approach just for ~1 week so it shouldn't be a problem

#

In that case, could you help us to troubleshoot an error we're getting?

#

We're getting ""You cannot create a charge with a PaymentMethod. Use the Payment Intents API instead." error while trying to use a Payment method created through setup intents on charges API. Is it probably an error on the body of the request, isn't it?

#

This is the body of the response

#

And this is the body of the charges API request
{
"description": "Solidus Order ID: xxxxxx",
"statement_descriptor_suffix": "xxxxx",
"card": "{PAYMENT_METHOD_ID Created through setup intent}",
"customer": "{customer_id}",
"payment_user_agent": "Stripe/v1 ActiveMerchantBindings/1.133.0",
"currency": "usd",
"amount": "100"
}

supple folio
#

Yeah

#

You can only use card_ id's with charges

#

Again recommend you just use payment intents

#

It's not that difficult to make the transition

#

But I can understand if you have a lot of code

#

It's just if you are already migrating to setupintents, it would be ideal to use payment intents in that same migration

bright peak
#

Yes we want to deploy in 'steps' mostly because of internal legacy code + old data migration. We think it would be safer doing it in steps. Our plan is: 1. Setup Intents + Charges. 2 data migration. 3 SetupIntents + Payment Intents

#

Would you be able to specify how to use a Setup Intent PaymentMethod with Charges api? 🙏 (I understand the risks and that it's not recommended)

supple folio
#

So I actually don't think this is possible

#

Sorry for misdirecting you

#

The issue is that setupintents create payment method objects

#

Not card_ or src_ obects

#

Which are what charges take

bright peak
#

Oh no. Ok Thanks, we'll need to rethink our migration strategy then