#Cjones
1 messages · Page 1 of 1 (latest)
tr_xxx and py_xxx are both objects created via a Transfer. Could you elaborate which specific field you want to have in the py object?
we have an invoice # generated by our system
currently we have it attached to the transfer statement description
but we are having trouble getting the invoice number to show on the py_ statement description
or simply 'description' field
Okie, can you provide an example Transfer id?
tr_1MP1cPH9YdMmPsAXBUXHxDwB
associated py_ showing in the connected account is py_1MP1cPIrZpG2QpUPG8EvMwoc
@viral sierra ?
Hi, looking...
Hmm if you call Retrieve on that py_ object, do you see anything could link to the Transfer?
let's expand balance_transaction just in case
I am not sure
can I also get the py_ # and add it to the transfer description?
@viral sierra are you still looking into this?
Hi, sorry I am juggling between threads. Yes I try to link the tr_xxx and py_xxx, but don't think you will have the py id right after created tr_
I am thinking of when you receive the webhook event payment_intent.created of py_xxx, does it have anything point back to the tr object
yes thats what I am wondering
oh wait, when you created the Transfer, don't you have destination_payment?
Let's try to update this Payment Intent with a metadata, contain any information you want
right after creating Transfer
and then apply it to the destination payment?
I need to pass this information to another dev that built this so can you give me a few steps I can pass to him
Sure, just use the Update Payment Intent against the destination_payment id (py_xxxx) you received after created Transfer.
Calling the API with metadata https://stripe.com/docs/api/payment_intents/update?lang=ruby#update_payment_intent-metadata
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
so we can update the description in (py_xxx) using this method?