Stripe Payment to Dataverse Order and Receipt

Overview

This flow turns successful Stripe payments into governed order records with automatic receipting. On a daily schedule it pulls the previous day's successful charges from the Stripe REST API, writes each one as a governed Stripe Order record in Dataverse, emails a branded HTML receipt to the customer via Outlook, and sends an internal sales notification to the finance team.

Why it matters: Payment data stuck in Stripe isn't in your system of record. Capturing every successful charge as a Dataverse order — with an automatic customer receipt and an internal alert — keeps finance, operations and customers aligned, and gives downstream automations (fulfillment, accounting, reporting) a clean order table to build on.

Status: Built · Ships Off (demo). Going live requires only: authorizing the two connections, setting the Stripe secret key env var, and (optionally) adjusting the company name / finance recipient.

Use Case

A business taking Stripe payments wants each successful payment logged in Dataverse as an order, the customer to receive a receipt automatically, and the finance team to be notified — without anyone copying data out of the Stripe dashboard.

Flow Architecture

Environment Variables

Connectors & Connections

Connector	API name	Actions used
HHTTP	http	GET /v1/charges
Microsoft Dataverse	shared_commondataserviceforapps	CreateRecord
Office 365 Outlook	shared_office365	SendEmailV2

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Switch to real-time

Replace the daily Recurrence poll with a Stripe webhook receiver (HTTP Request trigger) once a Stripe connection/webhook is available; verify the webhook signature with a flowlibs_StripeWebhookSecret env var.

Idempotency

Before Create Order Record, list the Stripe Order table filtered on flowlibs_chargeid and skip if it already exists, to guard against re-processing.

PDF receipts

Add the Word Online connector (CreateFileItem → GetFilePDF) to attach a branded PDF instead of the HTML body.

Tax/fulfillment

Branch off the order record to trigger invoicing or shipping.

Window/schedule

Change the Recurrence frequency or the charge query window (created[gte]/created[lt]).

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

@{div(sub(ticks(startOfDay(addDays(utcNow(),-1))),621355968000000000),10000000)}

@{div(float(items('Apply_to_each_Charge')?['amount']),100)}

@addSeconds('1970-01-01T00:00:00Z', items('Apply_to_each_Charge')?['created'])

@and(equals(items('Apply_to_each_Charge')?['status'],'succeeded'), equals(items('Apply_to_each_Charge')?['paid'], true))

@coalesce(items('Apply_to_each_Charge')?['billing_details']?['email'], items('Apply_to_each_Charge')?['receipt_email'], 'unknown@unknown.local')

Customize & download