> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fusioncore.us/llms.txt
> Use this file to discover all available pages before exploring further.

# Payment Confirmation

> Set up the managed Payment Confirmation component so Portal users see a receipt after a successful payment, including how to point it at the receipt URL field.

## Overview

The **Payment Confirmation** component shows a Portal user a summary of their transaction after a successful payment, including a link to their receipt. It is the managed `paymentConfirmation` component (Portal, `FCORE_PORTAL`), and it is the page the [checkout](/end-user-guides/portal/checkout-lwc/index) component redirects to after payment (via its **Payment Confirmation URL** property, default `FC_Payment_Confirmation__c`).

The component reads the relevant Financial Event from a UUID passed in the page URL, then displays its details and a receipt link. The confirmation number it shows is the Financial Event's name with the `FE-` prefix removed.

## Prerequisites

* A published Experience Cloud page for payment confirmation. See [Creating Portal Site Pages](/end-user-guides/portal/creating-portal-site-pages).
* A field on `FCORE_PAY__Financial_Event__c` that holds the receipt URL, populated before the user is redirected. The default field is `FS_Portal_View_Document_URL__c`.

## How to Configure the Payment Confirmation Page

<Steps>
  <Step title="Add the component to your confirmation page">
    Open your payment confirmation page in Experience Builder. Click the **Components** icon, search for **Confirmation**, and drag the **fusionCore: Payment Confirmation** component onto the page.

    <Frame>
      <img src="https://mintcdn.com/fusionspan/EW_gg4_8FJ-921wF/images/end-user-guides/4175462424/Screenshot_2025-02-05_at_8.49.13-PM.png?fit=max&auto=format&n=EW_gg4_8FJ-921wF&q=85&s=be5f038c26937b85435609b58ddd1557" alt="Adding the fusionCore Payment Confirmation component to a page in Experience Builder" width="1532" height="1442" data-path="images/end-user-guides/4175462424/Screenshot_2025-02-05_at_8.49.13-PM.png" />
    </Frame>
  </Step>

  <Step title="Set the receipt URL field">
    Select the component and set the **Receipt Document URL Field API Name** property (`receiptDocumentUrlFieldApiName`) to the API name of the field on `FCORE_PAY__Financial_Event__c` that holds the receipt URL. The default value is `FS_Portal_View_Document_URL__c`, which links to the financial-document Visualforce pages on the Financial Event. Click **Publish**.

    <Frame>
      <img src="https://mintcdn.com/fusionspan/EW_gg4_8FJ-921wF/images/end-user-guides/4175462424/Screenshot_2025-02-05_at_8.49.30-PM.png?fit=max&auto=format&n=EW_gg4_8FJ-921wF&q=85&s=d22e343dbecb2b14c870c5e60e5d8fdf" alt="Setting the Receipt Document URL Field API Name property on the Payment Confirmation component" width="2486" height="774" data-path="images/end-user-guides/4175462424/Screenshot_2025-02-05_at_8.49.30-PM.png" />
    </Frame>
  </Step>
</Steps>

## Limitations and Common Pitfalls

* **The receipt URL field must be populated before the redirect, or the page errors.** The component expects the field named in `receiptDocumentUrlFieldApiName` to already hold a value when the user lands on the page. Make sure your install order and automation populate that field before checkout redirects the user.
* **The configured field must be a real, queryable field on the Financial Event.** If `receiptDocumentUrlFieldApiName` names a field that does not exist on `FCORE_PAY__Financial_Event__c`, the component cannot load. Confirm the field exists before publishing.
* **The Financial Event must be `Type = Payment`.** The component throws an error for a Financial Event of any other type, because confirmation is meaningful only for a completed payment.
* **The receipt URL must be a real web link.** The value must begin with `http://` or `https://`; a path or bare text will not produce a working receipt link.
* **The page needs a UUID parameter.** The component loads its Financial Event from a UUID passed in the page URL. If the redirect omits that parameter, the page cannot find the transaction. Letting the checkout component handle the redirect supplies this automatically.