Skip to main content
The fusionCore: Wallet Items component lets a portal member view, add, and manage their saved payment methods on a Portal page. It is a thin managed wrapper that surfaces the Commerce wallet UI — the wallet screens, controllers, and the FCORE_PAY__Wallet_Item__c object all belong to the managed Commerce (FCORE_PAY) package. You can place the component and set its two properties, but you cannot modify the wallet UI or its behavior. A Wallet Item a member creates here is the same Commerce FCORE_PAY__Wallet_Item__c record that staff manage from the contact’s Wallet action. For how staff create, edit, and pay with Wallet Items, see Wallet Items Overview. The component exposes two properties:
  • Header (header) — the heading shown above the wallet.
  • Payment Provider Account Id (paymentProviderAccountId) — the Payment Provider Account (FCORE_PAY__Payment_Provider_Account__c) whose saved methods the wallet shows. This is not required; leaving it blank changes which methods render rather than producing an error.

​
Prerequisites

  • A configured and validated Payment Provider Account (FCORE_PAY__Payment_Provider_Account__c) for Stripe. See Stripe.
  • The FC_Portal_My_Wallet permission set is assigned to the portal members who will manage their wallet. It grants the record access and Commerce controllers the component relies on.

​
Setting Up the Wallet Item Component

1

Create the page

Make sure you have created a page with an appropriate title.
2

Add the Wallet Items component

Drag and drop the fusionCore: Wallet Items component onto the page. Give it an appropriate name and set the Payment Provider Account Id to the account whose saved methods the wallet should show.
The fusionCore: Wallet Items component placed on a portal page with its properties
3

Add the component registration

Drag and drop the FS Portal - Component Registration component onto the page. It registers the payment, wallet, and checkout-summary components — including the Stripe payment provider and payment method — into the fusionCore component registry so the wallet and checkout UI can load them at runtime. The component renders nothing itself, but a Stripe-backed wallet page needs it.
The FS Portal - Component Registration component placed on a portal page
4

Publish

Click Publish to save your changes.

​
Creating a Wallet Item as a Portal Member

Once the page is live, members save their own payment methods through it. A member can save a method while checking out, or add one directly on the My Wallet page.

​
Saving a method in checkout

1

Enter your payment information

On the Checkout page, fill out your payment information, then check the box below the payment details to save the method.
The Portal checkout payment form with the save-payment checkbox selected
2

Check out

Click Checkout to complete the payment and save the method.

​
Saving a method from My Wallet

1

Add a method on the My Wallet page

On the My Wallet page, click Add New Wallet Item for the business unit you want to save the method under.
The rendered My Wallet page in the portal, with a section per business unit and an Add New Wallet Item button in each

The My Wallet page as a member sees it

2

Select a payment method

Select the payment method you want to add.
The payment method selection step on the My Wallet page
3

Save the method

Enter the payment details, check the box below them to save the method, then click Save.
The payment detail form with the save checkbox selected

​
Limitations and Common Pitfalls

  • The wallet UI is managed and not customizable. This component wraps the managed Commerce wallet. You control its placement and its two properties only — the wallet UI and its code cannot be changed.
  • The wallet needs a configured Stripe account. The wallet draws its methods from a configured and validated Payment Provider Account (FCORE_PAY__Payment_Provider_Account__c). Without one, there is nothing for the wallet to show.
  • Members need the permission set. Without FC_Portal_My_Wallet, a portal member cannot view or manage Wallet Items even when the component is on the page.
  • Only Card and ACH are supported. As of version 1.5, members can save Stripe Card and ACH methods only.