Versions Compared
Version | Old Version 3 | New Version 4 |
---|---|---|
Changes made by | ||
Saved on |
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Tip |
---|
Welcome to KonectThank you for downloading Konect and considering our solution for your social payments. If you can't find what you are looking for in our Knowledge Base, please connect with us directly by raising a support ticket. |
Konect does not add any custom objects to the Nonprofit Success Pack and uses only native data structures to process payments, issue receipts, and provide donation landing pages.
Konect has been integrated natively with the Stripe payment gateway exclusively for all financial payment processing. Stripe offers a deep set of functional features Konect takes advantage of, such as Smart Retries, Fraud Protection, and Subscription Management.
The Salesforce Nonprofit Success Pack Data Model is shown below with a description of the most commonly used data objects within Konect.
Image Removed
Konect takes advantage of the below-described data objects to enable reliable and scaleable social payments:
Contact
- this represents any person being managed within Salesforce, such as a donor, member, or any other relevant stakeholder.Recurring Donation
- this represents the structure describing a regular donation gift with attributes such asSchedule
,Amount
,Frequency
Opportunity
- the Nonprofit Success Pack offers a range of record types forOpportunities
such asDonation
andMembership
. Konect is able to process payments for any of these record types.Payment
- this represents the actual payment record with a reference to theStripe
payment gateway transaction, related to theOpportunity
capturing the revenue. In cases whereRecurring Donations
fail to process, multiplePayments
might exist for each retry until successful.
Salesforce has published a significant volume of learning content to better understand the Salesforce Nonprofit Success Pack via its Trailhead Learning Platform, so this Knowledge Base does not aim to replicate this. We have, however, described the specific functions offered by Konect to extend the Nonprofit Success Pack.Maica is principally based on the Salesforce Service Cloud and the Nonprofit Success Pack digital platform as outlined in the below diagram. It's important to understand that any organisation, nonprofit or not, can utilise the features offered by the Nonprofit Success Pack, in particular Relationships and Households.

Our solution utilises a range of standard Salesforce data objects to enable user access to all Salesforce features as well as other functional solutions to sit side-by-side by the NDIS management platform.
The key data objects being used by Maica are listed below with a description of their purpose and relationship to other data elements within the solution.
Contact: represents a person, such as client, partner, supporter, referrer, guardian, etc
Account: represents an organisation, such as service provider, commercial partner, household, etc
Opportunity & Opportunity Product: tracks any potential revenue, such as service agreements, product sales, etc
Product & Price Book: defines the underlying product structure from the NDIS, including support category, support item number, purpose, etc
Case: represents any incoming enquiry, complaint, issue as well as a set of support coordination features
Service Contract: represents the actual delivery contract once a service agreement (via opportunity) has been finalised
Plan: represents the overall NDIS plan for a participant which is automatically synced from the NDIA via their APIs
Plan Budget: represents a plan's recorded budget items which are automatically synced from the NDIA via their APIs
Service Booking: represents a support category budget which can be created/amended directly from within Salesforce; also automatically synced to the NDIA
Booking Item: represents the individual budget items within a service booking which can be created/amended directly from within Salesforce
Invoice: represents the mechanism of entering completed services (either internal or external) which require automatic claiming from the NDIA
Invoice Line Item: represents an individual support item (product) which is to be automatically claimed from the NDIA
Payment Request: represents the mechanism for submitting an automated claim to the NDIA and triggering payment (once approved)
Related Pages
Filter by label (Content by label) | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|