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.
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.
When installing PosiPay using a YML script, you'll find that certain configurations are handled automatically, streamlining the setup process. However, there are additional configurations that require your manual input to ensure everything functions correctly. For those specific manual configuration steps, please see the link provided below for comprehensive instructions.
If you choose not to utilize the YML script for your configuration, please follow the detailed steps outlined below to successfully complete the setup process.
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
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.
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 the Experience Cloud communities.
Setup > Digital Experiences > Settings > tick Enable Digital Experiences > click Save
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.
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
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
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:
Required Fields
Gateway Account = Gateway ID
Payment Method = Credit Card; Direct Debit
Require CVC = TRUE
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:
Go to Setup > Home page
In the Quick Find box search All Sites and click Builder
The Community page should be accessible by Guest User
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
Display the following fields in the page layout.
Active
Bank Account Number
Bank Code
Display the following fields in the page layout.
Bank Account
Batch Status
Status Message
When Generated
Bank Reconciliation Status
Bank Statement Line
Settlement Date
Display the Generate Bank Slip, go to Page Layout > Mobile & Lightning Actions
Display the following field in the page layout.
Default Gateway Customer
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
Display the following fields in the page layout.
Customer Address
Customer Email
Customer ID
Customer Phone
Customer
Default Payment Source
Gateway Account
Display the following fields in the page layout.
Event ID
Event Status
Gateway Account
Raw Request
Webhook Event Object
Display the following fields in the page layout.
Amount Paid
Attempt Count
Gateway Event
Invoice Date
Invoice ID
Invoice Status
Payment Intent ID
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
Add the following Picklist Value in the Transaction Status field.
Canceled
Dispute Under Review
Display the Refund Payment, go to Page Layout > Mobile & Lightning Actions
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.
Check Date
Check Drawer
Payment Identifier
Payment Method
Receiving Bank Account
Status
Bank Reconciliation Status
Bank Statement Line
Settlement Date
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
Display the following fields in the page layout.
Description
Details
Source
Type
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
Bank Reconciliation Status
Bank Statement Line
Receiving Bank Account
Settlement Date
Display the following fields in the page layout.
Bank Account
Bank Statement Name
Date Reconciled
Status
Display the following fields in the page layout.
Amount
Bank Statement
Bank Statement Line Name
Description
Reconciliation Status
Settlement Date
Transaction Reference
Transaction Type
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
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
Click Save.
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.
If PosiPay is installed via a YML script, some configurations are automatically completed; however, others need to be set up manually. Please follow the configuration steps below.
This configuration is optional. If you wish to translate some field names or labels, follow this step.
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
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.
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.
Here is the PosiPay 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).
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
