Microsoft Dynamics 365 | Integration, Dataverse...

Stripe Integration via Power Pages / Dynamics

(1) Share

Report

Posted on by Barncliff-VA

When using the Stripe API to process payments for tickets via a Power Pages Dynamics portal, is it really not possible to set the transaction Description attribute?

Our supplier has deployed the Stripe API, and payments are being processed okay.

However they are coming through with a blank Description which isn't very helpful when reviewing and reconciling the data downloaded from Stripe.

Other Stripe transactional data has this attribute set, but that comes from different source systems.

I'm being told that you can't set the Description attribute in the Stripe Power Pages API. This seems quite an oversight so would like to confirm if this is actually the case?

It's the Description in the data that goes to Stripe that we need setting, our Dynamics' data is fine.

The Stripe documentation seems to suggest that it's possible to set the Description attribute, but elsewhere it appears not:

There is not enough payment gateway data in the Payment table – payment references and reason codes are not recorded.

Just like to confirm either way.

Categories:

Power Platform integration

All responses (2)

Answers (0)

Barncliff-VA 12 on at

Like (0)

Report

Stripe Integration via Power Pages / Dynamics

Thanks for taking time to reply :)

I think our supplier is using the standard Microsoft Power Pages Stripe integration.

Just seems rather odd that a description field wouldn't have been part of the basic MS solution, as it seems an obvious requirement alongside e.g. date, amount, etc.
Suggested answer

Muhammad Shahzad Sh... 542 Most Valuable Professional on at

Like (0)

Report
Stripe Integration via Power Pages / Dynamics

You can set the description attribute when creating a Stripe charge or PaymentIntent via the Stripe API — the Stripe API fully supports it, as documented by Stripe.
The limitation is not with Stripe, but likely:

With how the Power Pages Dynamics portal integration has been implemented (e.g., if the supplier's code or the custom connector is not passing the description field).

Or with the specific payment component being used (if it doesn’t expose description as configurable).

Ask your supplier to update their API request code to pass the description field when creating the charge/PaymentIntent.