Step 3 - Post-configuration

Owned by Jhetah Mae Leornas
Last updated: Oct 28, 2024
12 min read

Congratulations on installing PosiPay! After your initial installation, you are now able to configure the features to make them accessible.

Note: Do this after installing the latest package.

Grant Access to PosiPay

To have access to the PosiPay features, assign PosiPay’s Permission Set to a User with a System Administrator profile.

  • Go to Setup > Home page > Click Users under the Users section > Choose the user with the System Administrator profile

  • After clicking the User, click the Permission Set Assignment > Edit Assignments

image-20240312-073710.png

  • Choose PosiPay and click Add to Enabled Permissions Sets then click Save. The System Administrator now has access to all of the PosiPay objects and fields.

Enable Guest Access

For Stripe to be able to engage with PosiPay, we need to create the right environment that allows Stripe to speak to certain objects within PosiPay.

Enable Communities

Enable the Experience Cloud communities.
Setup > Digital Experiences > Settings > tick Enable Digital Experiences > click Save

Create Community Site

Create a site for Webhook

  • Go to Setup > All Sites > Click New > choose Build Your Own (Aura) > click Builder

  • Fill out the Name and URL

    • Name = Webhook

    • URL = webhook

  • Publish the site by clicking the Publish button.

  • Set the site to Public Access.

Webhook Guest User Profile Config

Enable Webhook Listener

In the next step, we will set up the webhooks from Stripe’s end, but first, you need to make sure you are configured to be able to listen to them correctly.

Create a new site for the Webhook List

  • In All Sites, click Builder next to the site you want to access.

  • Click Settings and select General.

  • Under Guest User Profile, click the profile name.

  • Click Apex Class.

  • Click Edit.

  • Enabled these Apex Classes

    • PosiPay.CommonFunction

    • PosiPay.StripeFormComponentController

    • PosiPay.WebhookListener

 

Webhook Object Access

Go to Setup > Click All Sites

  • In All Sites, click Builder next to the site you want to access.

  • Click Settings and select General.

  • Under Guest User Profile, click the profile name.

  • Click Object Settings.

  • Search for the Objects that you want to configure for the Guest User.

 

  • Gateway Event
    Click Edit and tick Read and Create under the Object Permissions as well as in Fields Permissions and click Save.

     

     

  • Gateway Account

     

  • PosiPay Log

  • Gateway Invoice

Create a Community Site for Stripe Form

  • Go to Setup > All Sites > Click New

  • Choose a template, for our Site, we choose Build Your Own (Aura).

  • Fill in the necessary information then click Create.

  • After doing so, click Builder.

  • Display the Stripe Form component.

  • Fill out the following fields below:

  • Click the Publish button in the upper right corner and it will show a confirmation message and click Publish.

After creating the Community Sites do the following configuration:

  1. Go to Setup > Home page

  2. In the Quick Find box search All Sites and click Builder

 

  1. The Community page should be accessible by Guest User

Manually Displaying Fields in Page Layout

Some fields need to be manually displayed in the page layout for some objects.

To display these fields follow this step:

Go to Set Up > Object Manager > search for the Object > Page Layout > click the specific layout > Drag and drop the fields to their corresponding areas > Save

 Bank Account

Display the following fields in the page layout.

  • Active

  • Bank Account Number

  • Bank Code

Bank Deposit Batch

Display the following fields in the page layout.

  • Bank Account 

  • Batch Status 

  • Status Message 

  • When Generated 

Display the Generate Bank Slip, go to Page Layout > Mobile & Lightning Actions

Contact

Display the following field in the page layout.

  • Default Gateway Customer 

Gateway Account

Display the following fields in the page layout.

  • API Token 

  • Accepted Card 

  • Accepted Currency 

  • Active 

  • Base URL 

  • Default Currency 

  • Description 

  • Enable 3D Secure 

  • Enable Live Payments from Sandbox 

  • Faud Trigger 

  • Gateway Provider 

  • Payment Method 

  • Publishable Key 

  • Sandbox 

  • Version 

  • Webhook Endpoint URL 

Display the Authenticate, go to Page Layout > Mobile & Lightning Actions

Gateway Customer

Display the following fields in the page layout.

  • Customer Address 

  • Customer Email 

  • Customer ID 

  • Customer Phone 

  • Customer 

  • Default Payment Source 

  • Gateway Account 

Gateway Event

Display the following fields in the page layout.

  • Event ID 

  • Event Status 

  • Gateway Account 

  • Raw Request 

  • Webhook Event Object 

Gateway Invoice

Display the following fields in the page layout.

  • Amount Paid 

  • Attempt Count 

  • Gateway Event 

  • Invoice Date 

  • Invoice ID 

  • Invoice Status 

  • Payment Intent ID 

Gateway Transaction 

Display the following fields in the page layout.

  • Adjustment Date 

  • Adjustment ID 

  • Amount 

  • Balance Transaction 

  • Charge ID 

  • Decline Code 

  • Flagged As Fraud 

  • Gateway Account 

  • Gateway Event 

  • Gateway Fee 

  • Gateway Invoice 

  • Order 

  • Payment Date 

  • Payment Intent Id 

  • Payment Method 

  • Process Type 

  • Refund Date 

  • Refund Id 

  • Result Code 

  • Result Message 

  • Risk Level 

  • Risk Score 

  • Settlement 

  • Source Transaction 

  • Transaction Currency 

  • Transaction Reference ID 

  • Transaction Status 

Display the Refund Payment, go to Page Layout > Mobile & Lightning Actions

Order

Add new picklist value in Status

Go to Set up > Object Manager > Order > Fields & Relationship > Status > Click New in Order Status Picklist Values

  • Add a new picklist value called “Paid” where the Status Category is “Activated”  

  •  Add a new picklist value called “Failed” where the Status Category is “Draft” 

     

Display the following fields in the page layout.

  • Payment Status

  • Check Date 

  • Check Drawer 

  • Payment Identifier 

  • Payment Method 

  • Receiving Bank Account 

  • Status 

 

Payment Source

Display the following fields in the Payment Source page layout.

  • Account Holder Name 

  • Active 

  • BSB Number 

  • Card Expiry Date 

  • Card Type 

  • Cardholder Name 

  • Default Payment Source 

  • Gateway Account 

  • Gateway Customer 

  • Last4 Digit 

  • Payer 

  • Payment Source Type 

  • Token 

PosiPay Log

Display the following fields in the page layout.

  • Description 

  • Details 

  • Source 

  • Type 

Gateway Settlement

Display the following fields in the page layout.

  • Amount 

  • Error Code 

  • Error Message 

  • Gateway Account 

  • Gateway Adjustment Total 

  • Gateway Fee Total 

  • Gateway Reconciliation Status 

  • Gateway Reference ID 

  • Gateway Refund Total 

  • Reconciliation Balance 

  • Reconciliation Date 

  • Starting After 

  • Stripe Fee Total 

Global Picklist

Payment Method

The only picklists are the following; otherwise, please remove them. 

  • Credit Card 

  • BECS Debit 

  • Cash 

  • Check 

  • Direct Deposit 

Go to Set up > Search for Picklist Value Set > Payment Method

Sharing Settings

Enabling the guest user to obtain access to the Gateway Account and Gateway Events records.

  • Go to Set up

  • In the Quick Find box search for Sharing Settings

  • Under the Sharing Rule section, look for Gateway Account Sharing Rules and Gateway Event Sharing Rules then click New.

Gateway Account Sharing Rule

Note: The same process will be set up in Gateway Account and Gateway Event.

Step 1: Rule Name

  • Label: Guest User Access

  • Rule Name: Guest_User_Access (Once the label is entered, the form should be automatically populated.)

Step 2: Select your rule type

  • Rule Type: Guest user access based on criteria

Step 3: Select which records to be shared

  • Field: Owner ID

  • Operator: not equal to

  • Value: Guest User ID

Step 4: Select the users to share with

  • Share with: Select the Guest User site (where the Webhook is setup)

Step 5: Select the level of access for the users

  • Access Level: Read Only

  1. Click Save.

Change Data Capture

Go to Set Up and search for Data Capture.
In the Change Data Capture search for Gateway Transaction (PosiPay__GatewayTransaction__c) and Bank Statement Line (PosiPay__BankStatementLine__c) . Add it as Selected Entities then click Save.

 

 

Translation Workbench

Enable Translation Workbench

Make sure that the Translation Workbench is enabled, if it is currently disabled enable it. To enable,

Go to Set up > Search Translation Workbench in the quick find box > Translation Language Settings

Add Translated Languages and Translator

Click Add to select the languages your organization supports and the users who are responsible for translating that language.

Choose the language you wish to add. Add translators for this language to the Selected List box and click Save. After translators have entered all translated values, check Active to make these translations available to your users.

To make users translators for this language, select them from the Available List and click add. Make sure you give all translators the "View Setup and Configuration" permission so that they can begin translating.

Select Language in your Org

Go to Set up > Language Settings > Enable platform-only languages - no default translations are provided for platform-only languages check box is ticked.

Then you can add languages that your org supports. Click Save after.

PosiPay STF File

Here is the PosiPay STF File.

Export STF File

Note: Do this step if you (the translator) don’t have an STF file; otherwise, if you do, then skip this step.

If you are a translator or if you don’t have a STF file yet for importing. You can export it and translate the words that are translatable for your org’s supported language.

Go to Setup>Translation Workbench>Export tick the Source radio button and press Export as STF.

(If User is a translator) An email will be sent to the email address that was setup from your org. This email contains the link to the STF file.

(If User is a translator) Click the latest STF file that the email sent (The provided example below shows many STF file, just ignore those as it is just an example, you will only have one STF file when first time).

After clicking the file it will now then prompt you to its detail page where you can also download it. Click View file to download the STF file.

(If User is a translator) The STF file that was exported contains all the translatable content of your org, you can now open and edit it using any of the following: Notepad ++, Excel, VsCode, Notepad or any other editor that can edit STF files.

(If User is a translator) The image below shows the example content of the STF file. To translate some text on it make sure to change the Language Code according to your org’s default language. Then you can now select words form content that you want to translate. Take note that when you translate only change those in the right side and not those in the left side, refer to the check mark in the image below, the check signifies editable area the ex is not.

(If User is a translator) You can now then remove those rows that are not included in your translation. It should look something like the image below (Take note that it only defers on the how many translated content that the translator has translated).

Importing the STF File

If the user has already the STF file, the user can just , go to Setup>Translation Workbench>Import Click the Choose File button then select your STF file. After selecting you can now then press Import.

After that, you should receive an email containing a success message if it is successfully imported and an error message if it is not successfully imported. The email should look something like the image below.

If success,

If failed,

 

Next place to go: Step 4 - Stripe Setup