#Andres2792-source

1 messages · Page 1 of 1 (latest)

winged tartan
#

Hi! Here you are
https://stripe.com/docs/api/cards/object
https://stripe.com/docs/api/sources/object

Stripe API reference – The card object – curl

Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.

Stripe API reference – The source object – curl

Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.

warm fiber
#

I know the attribute difference but in concept can they be used for the same? I'm having issued setting a card type source as default source for a subscription

winged tartan
#

What issue is that?

#

do you have a request id? req_xxx

warm fiber
#

Nope noticed that on DB as well, it's telling me card type sources are invalid to be set as default source for subscription but card objects work and I don't get the reason behind it

#

😅

winged tartan
#

I doubt that 🤔 Can I see the request id?

warm fiber
#

There is no req ID since I can't save or select other options as you can see the as they are greyed :(

#

I haven't tried this myself via API but I wasn't aware of that b4 so I decided to ask b4 trying it via API

winged tartan
#

How did they appear in the first place? Are they added via an integration and now you can't select on Dashboard?

warm fiber
#

Vía DB I'm using Payment Methods API

#

But DB tokrnize and create them as sources or card object

#

Depending how they got gathered

#

Ex hosted invoice page or DB card element

#

So I was also trying to see if I could use those objects from the hosted invoice page or tokenized on the DB directly

#

As default sources for specific subscriptions

#

Sorry to ask a lot lol I'm trying to create a list of features to implement in the ui I mentioned b4

#

This is an example of a customer with two card objects and two sources and only the card objects can be selected

20220807_224116.jpg
#

You still here @winged tartan ? :c

winged tartan
#

Sorry but it was not clear how you created those object. Canyou give an example request id that you sent to Stripe API?

warm fiber
#

I didn't did it, those objects were all created via Dashboard on the Subscription creation ui or via a payment through a hosted invoice page url @orakaro

winged tartan
#

ah DB mean Dashboard? I thought it's your Database

warm fiber
#

Ouch sorry for the misinformation from my side, yes DB - > Dashboard

winged tartan
#

I am not sure why it's invalid. Let's get a step back. What do you want to achieve specifically?

warm fiber
#

Be able to set specific sources, card objects or payment methods as default source/Payment method on specific subscriptions via Dashboard

winged tartan
#

So it's only about Dashboard right? What did you mean for "features to implement"

warm fiber
#

A to do list on my side ui for the subscription teams to "patch" the Dashboard missing options like the specific cancelation date

#

In this case I don't get why those sources are invalid :( and can't be set as default source via Stripe Dashboard if Stripe itself created them

winged tartan
#

In your todo list (I suppose it's your UI), how would it relate to this Dashboard page?

#

I am trying to grasp the usage

warm fiber
#

I would direct the team to handle what is posible in the Dashboard adding them as team members and what is not possible in my custom ui issuing the respective API calls in my back end

#

So I'm identifying what can be done on the Stripe Dashboard and what can't be done as well to create a custom implementation on my ui

winged tartan
#

I would say simply call Stripe Cancel API on a specific UTC, is way easier than what you want to do by

I would direct the team to handle what is posible in the Dashboard adding them as team members and what is not possible in my custom ui issuing the respective API calls in my back end

#

But yeah I am not sure why there are those invalid source

warm fiber
#

Yeah about the cancelation date yup, I'll issue the call from my back end but I'm in crisis with those sources since I don't create them

winged tartan
#

Can you give me their Ids to look at?

warm fiber
#

They are live objects is OK to share them here or should I poke Support?

winged tartan
#

Id is okie

#

just don't paste any key

warm fiber
#

Roger that... One sec

#

Card_1LG6a6EctRfiBmd6wthIuMHe -> working card object
Src_1JVSnmEctRfiBmd6POq0KTyM

#

Not working source example

winged tartan
#

can you also give the customer id?

warm fiber
#

Cus_K5IeYqDdtROl3H

#

There u go

winged tartan
#

I see *5338 selectable in the UI

#

Is this different Customer?

warm fiber
#

Yup

#

In the meantime is it possible to know why the Dashboard and hosted invoice page still uses sources if the recommendation is to use the Payment Methods API?

winged tartan
#

Dashboard API is different than public API 🙂

#

Dashboard API is just internal APIs that you don't (and shouldn't) worry of. We built it back when we had the Source API so that's maybe the reason

warm fiber
#

And should it be the reason behind this behavior? If is not public.... Well that mean I should relay on public endpoints and build a complete ui to handle my subscriptions on my side?

winged tartan
#

To serve you customer yes

warm fiber
#

Well then the internal team with Stripe Dashboard access seems to be discarded. But I find that source behavior odd

#

I will test card objects VS source objects via public endpoints and if it works well I'll forget the Stripe Dashboard for anything not related to the account itself

#

@winged tartan you can close this one :) and ty for your help in this hunt ;)