#shammah-destination-charge-fee

1 messages · Page 1 of 1 (latest)

worthy bobcat
#

@jaunty ember we don't set any of this automatically, if it's set, it's because your code explicitly set it

jaunty ember
#

The words "on_behalf_of" do not appear in the codebase. I wrote it.

worthy bobcat
#

do you have an example charge id

jaunty ember
#

py_1JqjZVAN9UGzw70gnONXIgQg

#

The only thing we are setting is the destination on the charge when we initiate it.

#

req_5on6FDR8w6oWzd is what created it. No on_behalf_of yet there it is on the charge when you fetch it.

worthy bobcat
jaunty ember
#

Because when you fetch the charge it has "on_behalf_of": "acct_1JcAwDEWll3SMyTF", as part of the data.

worthy bobcat
#

ah yeah sorry you're right That's because you use the legacy destination hash, which combined transfer_data and on_behalf_of

jaunty ember
#

What is the new hash?

worthy bobcat
#

transfer_data is what you want if you don't want on_behalf_of

jaunty ember
#

Thank you. TypeScript autocomplete got me there.

#

Or something. I'm not even sure how that happened

#
      /**
       * An arbitrary string which you can attach to a `Charge` object. It is displayed when in the web interface alongside the charge. Note that if you use Stripe to send automatic email receipts to your customers, your receipt emails will include the `description` of the charge(s) that they are describing.
       */
      description?: string;

      destination?: ChargeCreateParams.Destination;

Would be nice if this was marked deprecated

worthy bobcat
#

agreed but we don't really do this today unfortunately

jaunty ember
#

Thanks, this should solve the issue.