#sina

1 messages · Page 1 of 1 (latest)

versed cloudBOT
cyan bay
#

Hey there, yes that's correct.

alpine tiger
#

Awesome, thanks!

#

I got the following error when trying to specify an acceptance type of offline:

"Offline mandate customer acceptance data is not supported by acss_debit payment method type"

cyan bay
#

Hmm can you share a request ID for that?

#

And let me double check. I often do mix up the nuances of the different debit methods and what supports which attributes

alpine tiger
#

pi_3LpaK2E48Fm17Noq152zMUw7

cyan bay
#

Sorry, server is busy

#

Looking

#

Ah okay

#

Yeah so looks like this isn't supported by default

alpine tiger
#

Thanks I will do that. If I have questions about unrelated topics should I start a new thread?

cyan bay
#

Nope you can ask here

alpine tiger
#

We are a platform account using Destination charges with Connected accounts. We want to implement the API report Connected account itemized date-ranged payout reconciliation https://stripe.com/docs/reports/report-types#schema-connected-account-payout-reconciliation-itemized-5
into our UI.

It's important that each row references our internal order/transaction ID. I thought we would be able to do this easily using either the payment or transfer metadata. But it seems that with the automated flow of funds from Destination charges, the metadata is wiped when the transfer is created.

Understand the report types available via the Reporting API.

pliant moth
#

You should be able to get payment_metadata[key] if there are metadata k/v pairs on the Payment Intent

alpine tiger
#

For provided identifiers in report run for account acct_1KJJ0c2QUNSZUt6F results (frr_1Lp7UlE48Fm17NoqZPOxujzH) cant find any resource metadata (charge, payment intent, balance transaction).

#

The metadata key is s_invoice

pliant moth
#

Those are all transfers, so if transfers are the only thing showing up then you'll need to add the metadata to the Transfer object, instead of the Payment Intent

alpine tiger
#

But the transfer object is made automatically by Stripe during the destination charges flow. How could we add metadata to the Transfer object?