Payments2Us ManualsRecent Updates

Recent Updates

  • Updated on: Jan 27, 2019

    What is required to use Batch Entry

  • Procedure How to change the email text describes how to update and clone a Visualforce email template.

    When editing the Visualforce email template, there is a line that references a Visualforce component.  This begins with <AAkPay:.... The component can accept a number of parameters and these are documented below.

  • Turn this workflow on if you wish to be notified of all new Membership/Subscription Payments are made.

    Quick Steps:

    1. Locate workflow: New Online Membership Payment Notification
    2. Update the recipient of the workflow email
    3. Enable this workflow
  • Turn this workflow on if you wish to be notified of all new online payments (exception memberships).

    Quick Steps:

    1. Locate workflow: New Online Payment Notification
    2. Update the recipient of the workflow email
    3. Enable this workflow
  • Updated on: Dec 11, 2018

    How to activate Refund approvals

    Payments2Us comes with a basic approval process for refunds. By default, refund approvals process is not enabled and this procedure walks you through how you can do this.

    If you wish to have multi-level and more advanced approvals, you can setup Approval Workflows to do this.  The final approval step simply needs to do a field update that checks the "Approved" checkbox on the Payment Txn.  For setting up Approval workflows, please consult the Salesforce online help, or alternatively just use the more simpler version enabled in this procedure.

    For organisations wanting to use Refund Approval Processes, we recommend you review the internal security setup procedure.  You need to ensure that only approvals have update access to the Approval field on the Payment Txn Object.

    Quick Steps:

    1. Locate workflow: Refund Approval
    2. Update the recipient of the workflow email
    3. Enable this workflow
  • The Batch Payment Processor is activated from the “Start” button on the Merchant Facility and processes new transactions every 10 minutes.  This workflow is used to notify if the Batch Payments Processor has been started, but for some reason is no longer working.  This scenario should never happen, but sometimes can be caused by Salesforce.com maintenance.

    If the Recurring Payment Processor is running, it will do daily checks to ensure the Batch Processor is running if it should be running.  These checks should reduce the need to have this workflow reminder rule setup.

    Quick Steps:

    1. Clone Workflow rule " Batch Payment Processor Not Running [ADD TIME BASED WORKFLOW]" and rename to "Batch Payment Processor Not Running"
    2. Add a Time-Dependant Action. Set it to fire 1 day after Rule Trigger date.
    3. Add Action - Use existing workflow - "Email Alert: send reminder that Batch Payments Processor has been stopped and should be restarted [UPDATE WHO RECEIVES THIS NOTIFICATION]"
    4. Update the recipient of the Email Action "Email Alert: send reminder that Batch Payments Processor has been stopped and should be restarted [UPDATE WHO RECEIVES THIS NOTIFICATION]" to be a contact in your organisation that will follow up this email alert.

     

  • The Batch Payment Processor is activated from the “Start” button on the Merchant Facility and processes new transactions every 10 minutes. This workflow is used if the Batch Payment Processor has been running and has been turned off for more than 24 hours.

    Quick Steps:

    1. Clone Workflow rule " Batch Payments Process Restart Reminder [ADD TIME BASED WORKFLOW]" and rename to "Batch Payments Process Restart Reminder"
    2. Add a Time-Dependant Action. Set it to fire 1 day after Rule Trigger date.
    3. Add Action - Use existing workflow - "Email Alert: send reminder that Batch Payments Processor has been stopped and should be restarted [UPDATE WHO RECEIVES THIS NOTIFICATION]"
    4. Update the recipient of the Email Action "Email Alert: send reminder that Batch Payments Processor has been stopped and should be restarted [UPDATE WHO RECEIVES THIS NOTIFICATION]" to be a contact in your organisation that will follow up this email alert.
  • This workflow setup is required only if you are using recurring payments.  The recurring payments run a scheduler that can be easily started or stopped by an authorised person from the Merchant Facility Tab.  This time based workflow creates a reminder in case the processor is stopped and someone forgets to restart it again.

    Quick Steps:

    1. Clone Workflow rule "Recurring Payments Restart Reminder [ADD TIME BASED WORKFLOW]" and rename to "Recurring Payments Restart Reminder"
    2. Add a Time-Dependant Action. Set it to fire 1 day after Rule Trigger date.
    3. Add Action - Use existing workflow - "Email Alert: send reminders that Recurring Payments Processor has been stopped…"
    4. Update the recipient of the Email Action "Email Alert: send reminders that Recurring Payments Processor has been stopped…" to be a contact in your organisation that will follow up this email alert.
  • Updated on: Nov 25, 2018

    How to set up recurring payments

    Please note, this workflow is ONLY required if you wish to use the Variable Recurring Payments process and want to have the recurring payments processed automatically after they transactions are generated.

    This workflow is generally superseded by using the Regular Recurring Payment option (as defined on the Payment Form related to the Merchant Facility Tab).  This is the default option for all new installations of Payments2Us.

    Salesforce already comes with workflow templates that cannot be altered. These instructions show how to create a copy of the template which is then updated to suit Payments2Us functionality.

    This workflow reminds administrators to restart the Recurring Payment Processor, such someone stop the Recurring Payment Processor, but for some reason forgets to restart it within 1 day.

    Salesforce already comes with workflow templates that cannot be altered. These instructions show how to create a copy of the template which is then updated to suit Payments2Us functionality.

    Quick Steps:

    1. Clone Workflow rule "Payments - Recurring Process [ADD TIME BASED WORKFLOW]" and rename to "Payments - Recurring Process"
    2. Add a Time-Dependant Action. Set it to fire 1 hour after Rule Trigger date.
    3. Add Action - Use existing workflow - "Field Update: set Status Payment Start"