#siva.karicheti

1 messages · Page 1 of 1 (latest)

pallid cedarBOT
#

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

formal cave
#

Payment Intents use charges internally

#

Payment Intents are a stateful wrapper around charges, more or less

near spear
#

we are using legacy charges api now where we pass amount,currency,customer, Netsuite invoice id in metadata .. we dont pass the source

#

what ever is customer default source that will be used in payment

#

if payment source is card .. the response was immediate and if it fails we update our Netsuite invocie with failed message and later we will add to customer default source as meta data (charge failed) so that next payment added by customer will be default

#

now how I need to proceed with this payment intent ? I heard sources also going to depreciate ..we have to use payment methods ?

formal cave
#

Yes, we recommend using Payment Methods, though the API is backwards compatible with Card sources, too.

#

When using the Payment Intents API a payment_method must always be specified (or provided via Elements), there is currently no equivalent behaviour to the default_source behaviour you describe.

near spear
#

ohh okk.. if customer has 2 or 3 payment methods .. how we will we know which payment method we need to use ?

#

if e are going for payment intent ?

#

even I make one card as default source it is not showing in payment methods results

#

if customer adds new payment source by default it used to be default earlier .. now it is not happeing.

#

payment intent api is not immediate success like charge .. do we track the status ?

formal cave
#

You can record in your systems or customer metadata a preference for a "default" you should use

#

Or you can detach others and only keep one attached, depending on if you'd expect to use the others

near spear
#

if customer has one source and if he adds another at the same time adds meta data "invoice failed" to previous source .. the new source will become default ?

formal cave
#

Can you rephrase or share an example? I'm not sure what you mean, and in any case those source behaviours are not applicable to PMs and payment intents