Features
- The public forms do not allow members to update their details in Salesforce. Thankfully, the Batch Processor can be set up to take the values that are stored from the payment form and update Accounts and Contacts.
- Set up all your payment forms using the Demo Merchant Facility, then when you are ready to go live, just switch out the payment facility.
- A special frequency of “One-off – Authorise” can be used to charge a small amount up front, then charge the full amount using the Recurring Payment – Tokenise Charge facility later (as credit card details are not stored in your SF). Eg paying a deposit for an event, and charging the full fee on the day.
- You can also do a one-off charge to their card via Credit Card Token Payment. Make sure you have authorisation to do so.
- You can't do recurring payments with Paypal.
- You can do recurring payments with a variable amount that you have to manually set before each transaction occurs. I can't think of a business reason for this yet.
- You can do recurring payments as a payment schedule that emails the payee with a link to the payment form to ask them to pay now.
- For recurring payments. card expiry dates are stored in encrypted fields. The recurring payments processor will update a flag when the card is 30 days out from expiring and this will trigger an internal workflow to ask staff to contact the payee. You can update the card details or expiry date on the recurring payment.
- You can add manual payments or set up a recurring payment from the contact record.
...
- I was creating a form that was payment for an Event, but it was not using the Events functionality (custom events website). I was still seeing the back button on the checkout form, which is weird (the Back button is only for Events). It turns out it was because the Transaction Source field was set to Event. As soon as I set it back to Checkout, the back button was gone.
Amounts
- My Total Charged Amount was not showing correctly. I had to make sure all the amount fields were filled in and not null. The culprit for me was that the Freight field was null.
Opportunities
- Check Create Opportunity on the MF.
- Set the Opportunity Record Type in the PT.
- Choose Enable Soft Credits in the PT (if you are using Non Profit Starter Pack).
- Create fields on the Opportunity to match any custom fields you had on the Payment Transaction. These will be automatically updated on the Opportunity when it is created.
- Don't like the Opportunity Name as default? Then create a workflow to update the name to what you want. The prefix for the Opportunity Name comes from the Payment Type field on the PT.
Matching
Auto Match
- Will work if either Batch Payment Processor is started - works every 10 minutes OR
- Will work automatically if Batch Payment Processor is stopped AND
- Will work if the MF Automatic Matching field is not set to Do Not Match.
URL Tokens
Wow, URL Tokens are so powerful. You can create almost any type of payment as a custom form.
...
| For | Notes | PmtTxn | Field Set | Permissions | URL Token | Opportunity |
|---|---|---|---|---|---|---|
| Add the field to the PmtTxn object | Add the field to one of the custom fields field sets | Ensure sites public access profile has read / write permissions | Add the file to the URLToken Object | Add the field to the Opportunity Object | ||
| Client to Fill in | A custom field shown on the payment form and the client fills it in. |
|
|
|
|
|
| Pre-filled for Client | A custom field shown on the payment form and it is pre-filled |  | | |
Pre-fill the value on the URL Token | |
| Internal | A field on the PmtTxn that you need to see on the Opp eg you want the PmtTxn Number to appear in the Opportunity Name. Create a new field on the PmtTxn named Opp_PmtTxn__c Create a new field on the Opp named Opp_PmtTxn__c Create a workflow on create of the PmtTxn to update the Opp_PmtTxn__c to the value of the PmtTxn Nubmer. Create a workflow on create of the Opp to include the Opportunity.Opp_PmtTxn__c field in the Opp Name | |  | If using Batch Processor | | |