#melarts

1 messages ยท Page 1 of 1 (latest)

ivory knotBOT
sour plank
#

Hi there ๐Ÿ‘‹ are you working on building a scenario using Connect by chance?

slender falcon
#

I'm sorry what do you mean by building a scenario ?

sour plank
#

The process or flow that you're building, does it use Stripe Connect?

Or, could you provide one of the py_ IDs that you weren't expecting to see?

slender falcon
#

Yes we use stripe connect

sour plank
#

Can you share the ID of one of these py_ objects so I can take a closer look at the flow that you're using?

slender falcon
#

PAyment intent : pi_3MM8OrA69XfgDO9E0Jsf1Jch

#

charge : py_3MM8OrA69XfgDO9E0rkfhmVp

sour plank
#

Thank you, that helps me see exactly what you're referring to.

Those objects essentially are Charges, as they should still have the same structure of Charges and are interacted with via the same endpoints. Is that not the behavior that you're seeing?

slender falcon
#

I know there are charges but I want to know if they are specific to the payment method (klarna/giropay/bancontact) I chosed or If it can happen to have such id in other situation. And I see nowhere in the official documentation some explanations on py_.

agile obsidian
#

Hello ๐Ÿ‘‹
Taking over for toby as they need to step away soon

#

AFAIK Charge objects with py_ prefix are usually generated for non-card payment methods.

#

that shouldn't affect the way objects work with the APIs

slender falcon
#

On my current app I used to parse my data to display the charges by searching the prefix "ch_" but now with these new kind of payment method I feel I need to parse the prefix with "py_" too right ? And same for the refund, it is "pyr" and not "re_" ?

#

Is there a way to find a documentation?

agile obsidian
#

On my current app I used to parse my data to display the charges by searching the prefix "ch" but now with these new kind of payment method I feel I need to parse the prefix with "py" too right ? And same for the refund, it is "pyr" and not "re_" ?
That's correct

Is there a way to find a documentation?
I don't think we have public docs on this unfortunately as typically folks don't rely on prefixes as such. Your usecase is quite unique.

slender falcon
#

Ok perfect. I just want to make sure that py_ is very specific for non-card payment and not other stuff

#

my fear was to parse py_ and get data that I don't want

agile obsidian
#

No worries, I totally understand. Yes, py_ prefixed charges are used for non-card payments

slender falcon
#

perfect thanks a lot!

agile obsidian
#

NP! ๐Ÿ™‚ Happy to help