When adopting Konect, it is likely that a need will exist to migrate single and regular donors to Konect and Stripe, including payment methods such as Credit Cards. This article outlines the migration process from an existing payment gateway(s) to a single consolidated Stripe payment gateway. We have illustrated the various steps involved and anticipated responsibilities alongside indicative timelines.
Detailed Migration Process
The following table further details each step of the process. Konect allows you to work with any Salesforce implementation partner; we recommend Vertic in Australia.
Step
Name
Responsibility
Description
1
Export Contacts
Client Team
The initial step is to export all required Contact records from the existing fundraising solution; this export must include the Ids relating a specific contact to the existing payment gateway details.
2
Export Recurring Gifts
Client Team
The initial step is to export all required Recurring Gift records from the existing fundraising solution; this export must include the Ids relating a specific contact to the Recurring Gift.
3
Import Contacts
Partner
This step imports the exported Contacts from the existing fundraising solution into Salesforce, including the Ids exported in Step 1, as these will be used to match Contacts in Salesforce to the newly tokenised payment methods.
4
Import Recurring Gifts
Partner
This step imports the exported Recurring Gifts from the existing fundraising solution into Salesforce, including the Ids exported in Step 2, as these will be used to match Contacts to Recurring Gifts.
5
Export Payment Methods
Existing Gateway
The extraction of all relevant existing payment methods must include the same Id (Token) used in Step 1, as this is the same Id used to match the newly tokenised payment methods.
This involves a process of producing a sample file to verify the format of the eventual full export file.
6
Tokenise Payment Method
Stripe
The Stripe payment gateway will accept the exported payment method file (to an agreed format) and tokenise the submitted payment methods; further details on this can be found here.
7
Register Payment Information
Stripe
Once the existing payment methods have been tokenised within the Stripe payment gateway, they are registered within this gateway for future use.
8
Produce Import File
Stripe
This step produces the required import file for loading into Salesforce, containing the new Stripe payment methods token as well as the Ids exported in Step 1, as this is how we will match Contacts in Salesforce to Stripe payment methods.
9
Import Tokens
Partner
Partner will load the newly tokenised payment methods into Salesforce and use the Ids exported in Step 1 to match these to Contacts imported in Step 3.
It must be noted that there is potential loss of payment methods via a number of issues, such as incorrect details, expired cards, import issues, etc. The aim is to maximise success but accept some level of loss.
10
Match Contacts
Partner
Partner will use the Ids exported in Step 1 to match Contacts in Salesforce to the newly tokenised Stripe payment methods.
11
Create Subscriptions
Partner
Partner will create Stripe subscriptions to sync the newly imported Recurring Gifts in Step 4 with Stripe to enable payment processing.
Additional Information
The Maica solution has been integrated natively into the NDIS digital systems. In order to enable this connection, a number of technical steps are required as outlined in this article. The Maica (and Vertic) team will assist our client’s technical teams to complete these steps.
Technical Questionnaire Complete
The first step in the onboarding process is the completion of a technical questionnaire for submission to the NDIS. We have completed the majority of the technical questions and only require our clients to provide some organisational details. Please complete the Onboarding Survey so we can submit the questionnaire on your behalf.
Action: Please complete the Onboarding Survey to enable us to submit the technical questionnaire to the NDIS on your behalf.
PRODA Membership
The next step is to be set with a PRODA account. PRODA is essentially the authentication mechanism to access the NDIS APIs and digital systems; think of it like logging into an online service with your Google account.
Action: Please register both Production and Development accounts with PRODA.
To register for PRODA accounts, use the following links:
Once your PRODA account has been set up (both for Production and Development), you will need to add the Maica team as a Member to your PRODA account, as per the following steps:
Log into your PRODA account
Select
OrganisationsSelect your organisation’s profile
Click
MembersClick
Add Memberand use the following details to add Vertic to your PRODA accountFor
ProductionuseRA Number:
9513734889Surname:
Tenenberg
For
Developmentuse:RA Number:
7362628939Surname:
Kent
Once the Vertic team has been added as a Member, please provide the following permissions:
Device-ManagementService-Link-ManagementOwner-Access
This access will enable our team to set up and manage all required configurations on your behalf. If you are uncomfortable to provide this access, you can manage devices and services yourself (guided by the Vertic team).
Action: Add the Vertic team to both your PRODA Production and Development accounts.
| Note |
|---|
Please note that the security code to log into the PRODA |
NDIS Portal Access
The last step in the onboarding process is to include Vertic into your NDIS API Developer portal. As with PRODA, there are also two environments with this portal, as per the below:
NDIS Development API Portal (Development)
NDIS Development API Portal (Production)
| Tip |
|---|
Users can’t be created online for this portal and access is granted by sending an email to When registering for the NDIS Development Portal, you will need to provide some details for the Vertic team as the Nominee which we have outlined below:
|
Once you have access to the NDIS Developer Portal (both Development and Production), the Vertic team needs to be invited as a App Developer using the following steps:
Log into the NDIS Developer Portal as per the links above for either Development or Production
In the top right, select your
Account->My OrganisationClick
Add Userand enter the following details:New User’s Email Address:
developer+<<Your Organisation Name>>@vertic.com.auso, for example forMaica, the user’s email address would bedeveloper+maica@vertic.com.auSelect
App Developeras the Role
Action: Create accounts on both NDIS API portals and add the Vertic team.
Related Pages
| Filter by label (Content by label) | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|