cme-issuing-auths

[drifting apex]

Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

• cme-authorization-metadata, 17 hours ago, 11 messages

[covert sierra]

Are the docs wrong?

[unborn venture]

Hello! On evt_1ONaBuLU8jzNaTZmBvUDQYcz which metadata specifically are you referring to? Are you talking about the member_id?

[covert sierra]

Yes

In the response body there's also "hello":"there"

[unborn venture]

That's metadata that has been set on the Issuing Cardholder, not the Issuing Authorization. That metadata was also removed in the past few days (see https://dashboard.stripe.com/test/logs/req_hgjytspaGcAB6R)

[unborn venture]

The "hello": "there" is just something that's returned from your own server - it's not actually being set on any stripe object

Actually I may be wrong about the hello/there thing - let me just double check

Is there a reason you responded with amount in the body? You should only be passing that if pending_request.is_amount_controllable: true

[covert sierra]

Where are you seeing that?

And any solution on the metadata?

[unborn venture]

We talk about the webhook format here: https://stripe.com/docs/issuing/controls/real-time-authorizations#webhook-response

If the authorization’s pending_request.is_amount_controllable property is true, you can provide this value to control how much to hold for the authorization. It must be positive.

I believe it's not working because you're incorrectly passing in amount so we consider the whole response to be invalid

[drifting apex]

cme-issuing-auths

[covert sierra]

Okay thanks