admin

About admin

This author has not yet filled in any details.

admin has created 60 entries.

Entries By admin
  • LawPay Integration with salesforce

    What is LawPay?

    LawPay provides easy-to-use payment solutions that take the work out of getting paid. From sending payment requests and tracking payments to protecting your IOLTA account and integrating with your favorite legal software products—LawPay has you covered.

    LawPay Features:

    • Payment Pages
    • Quick Bill
    • Scheduled Payments
    • Comprehensive Reporting
    • Custom Dashboard
    • Scheduled Payments
    • Integrated Partners
    • Integrate Payments into Your Website

    LawPay integration:

    1: Configure your partner OAuth application

    • In the web application, click your name in the top-right corner and click Developers. (This part of the web application is available only to users with the Administrator or Developer role and to the merchant owner.)

    • The My Partner Applications section on the right lists your partner OAuth applications.   Locate the partner OAuth application that corresponds to your application and click Edit.

    • Set the application name. For current merchants, this is the name your customers see when they authorize your partner OAuth application to interact with their AffiniPay, CPACharge, DesignPay, or LawPay account.
    • Ensure that OAuth Enabled is selected. OAuth is required for all integrations. Do not uncheck this checkbox.

    2: Request an access token

    You must get permission from your users to perform transactions on their behalf, using the OAuth 2.0 authorization code flow. Here’s a high-level description of this flow:

    • In your application, a user (who is an AffiniPay, CPACharge, DesignPay, or LawPay merchant) clicks a Connect button.
    • The user’s browser is redirected to a page that prompts the user to give your application access to the user’s AffiniPay, CPACharge, DesignPay, or LawPay merchant account.

    • After your application is granted access, the user’s browser is redirected to your web server, with a URL that includes an authorization code.
    • Your application requests an access token in exchange for the authorization code.
    • Your application receives an access token.

    Connecting with API keys :

    When you run transactions through the AffiniPay Payment Gateway, you need your:

    • Public key that identifies you to AffiniPay.
    • Secret keys that authenticate API requests made on your behalf.
    • Account IDs that specify the credit account or eCheck account associated with each transaction.

    To access your public key, secret keys, and account ID:

    • In the web application, click your name in the top-right corner and click Developers. (This part of the web application is available only to users with the Administrator or Developer role and to the merchant owner.)

    • Click Authorize Application, select My Website from the drop-down list, and click Authorize Application.

    • Locate My Website in the Authorized Applications grid, and click Show Credentials to see your public key, secret keys, and account ID. You’ll need all three to create a charge through the AffiniPay Payment Gateway API

    Creating payment forms using hosted fields:

    AffiniPay hosted fields protect your payment page by tokenizing payment information. They provide SAQ-A PCI compliance, the highest level of PCI compliance. Hosted fields are <iframe> elements sourced from AffiniPay’s servers that contain a single corresponding <input> element. These iframes replace the input elements on your form that contain payment information.

    To create a payment page with hosted fields:

    1. Add a reference to the AffiniPay hosted fields JavaScript library
    2. Create a payment form
    3. Create a hosted fields configuration object
    4. Style the hosted fields
    5. Create a user-defined callback
    6. Initialize hosted fields
    7. Get a payment token

    Example page: eCheck payments:

    Results:

    • Make Echeck payment easily.
    • Increase productivity
    • Improve the customer experience

  • LawPay Integration with salesforce

    What is LawPay?

    LawPay provides easy-to-use payment solutions that take the work out of getting paid. From sending payment requests and tracking payments to protecting your IOLTA account and integrating with your favorite legal software products—LawPay has you covered.

    LawPay Features:

    • Payment Pages
    • Quick Bill
    • Scheduled Payments
    • Comprehensive Reporting
    • Custom Dashboard
    • Scheduled Payments
    • Integrated Partners
    • Integrate Payments into Your Website

    LawPay integration:

    1: Configure your partner OAuth application

    • In the web application, click your name in the top-right corner and click Developers. (This part of the web application is available only to users with the Administrator or Developer role and to the merchant owner.)
    • The My Partner Applications section on the right lists your partner OAuth applications.  Locate the partner OAuth application that corresponds to your application and click Edit.
    • Set the application name. For current merchants, this is the name your customers see when they authorize your partner OAuth application to interact with their AffiniPay, CPACharge, DesignPay, or LawPay account.
    • Ensure that OAuth Enabled is selected. OAuth is required for all integrations. Do not uncheck this checkbox.

    2: Request an access token

    You must get permission from your users to perform transactions on their behalf, using the OAuth 2.0 authorization code flow. Here’s a high-level description of this flow:

    • In your application, a user (who is an AffiniPay, CPACharge, DesignPay, or LawPay merchant) clicks a Connect button.
    • The user’s browser is redirected to a page that prompts the user to give your application access to the user’s AffiniPay, CPACharge, DesignPay, or LawPay merchant account.
    • After your application is granted access, the user’s browser is redirected to your web server, with a URL that includes an authorization code.
    • Your application requests an access token in exchange for the authorization code.
    • Your application receives an access token.

    Connecting with API keys :

    When you run transactions through the AffiniPay Payment Gateway, you need your:

    • Public key that identifies you to AffiniPay.
    • Secret keys that authenticate API requests made on your behalf.
    • Account IDs that specify the credit account or eCheck account associated with each transaction.

    To access your public key, secret keys, and account ID:

    Log in to the web application that corresponds to the product you’re integrating into your application.

    In the web application, click your name in the top-right corner and click Developers. (This part of the web application is available only to users with the Administrator or Developer role and to the merchant owner.)

    Click Authorize Application, select My Website from the drop-down list, and click Authorize Application.

    Locate My Website in the Authorized Applications grid, and click Show Credentials to see your public key, secret keys, and account ID. You’ll need all three to create a charge through the AffiniPay Payment Gateway API

    Creating payment forms using hosted fields:

    AffiniPay hosted fields protect your payment page by tokenizing payment information. They provide SAQ-A PCI compliance, the highest level of PCI compliance. Hosted fields are <iframe> elements sourced from AffiniPay’s servers that contain a single corresponding <input> element. These iframes replace the input elements on your form that contain payment information.

    To create a payment page with hosted fields:

    1. Add a reference to the AffiniPay hosted fields JavaScript library
    2. Create a payment form
    3. Create a hosted fields configuration object
    4. Style the hosted fields
    5. Create a user-defined callback
    6. Initialize hosted fields
    7. Get a payment token

    Example page: eCheck payments:

    Results:

    • Make Echeck payment easily.
    • Increase productivity
    • Improve the customer experience

  • LawPay Integration with salesforce

    What is LawPay?

    LawPay provides easy-to-use payment solutions that take the work out of getting paid. From sending payment requests and tracking payments to protecting your IOLTA account and integrating with your favorite legal software products—LawPay has you covered.

    LawPay Features:

    • Payment Pages
    • Quick Bill
    • Scheduled Payments
    • Comprehensive Reporting
    • Custom Dashboard
    • Scheduled Payments
    • Integrated Partners
    • Integrate Payments into Your Website

    LawPay integration:

    1: Configure your partner OAuth application

    • In the web application, click your name in the top-right corner and click Developers. (This part of the web application is available only to users with the Administrator or Developer role and to the merchant owner.)
    • The My Partner Applications section on the right lists your partner OAuth applications.  Locate the partner OAuth application that corresponds to your application and click Edit.
    • Set the application name. For current merchants, this is the name your customers see when they authorize your partner OAuth application to interact with their AffiniPay, CPACharge, DesignPay, or LawPay account.
    • Ensure that OAuth Enabled is selected. OAuth is required for all integrations. Do not uncheck this checkbox.

    2: Request an access token

    You must get permission from your users to perform transactions on their behalf, using the OAuth 2.0 authorization code flow. Here’s a high-level description of this flow:

    • In your application, a user (who is an AffiniPay, CPACharge, DesignPay, or LawPay merchant) clicks a Connect button.
    • The user’s browser is redirected to a page that prompts the user to give your application access to the user’s AffiniPay, CPACharge, DesignPay, or LawPay merchant account.
    • After your application is granted access, the user’s browser is redirected to your web server, with a URL that includes an authorization code.
    • Your application requests an access token in exchange for the authorization code.
    • Your application receives an access token.

    Connecting with API keys :

    When you run transactions through the AffiniPay Payment Gateway, you need your:

    • Public key that identifies you to AffiniPay.
    • Secret keys that authenticate API requests made on your behalf.
    • Account IDs that specify the credit account or eCheck account associated with each transaction.

    To access your public key, secret keys, and account ID:

    Log in to the web application that corresponds to the product you’re integrating into your application.

    In the web application, click your name in the top-right corner and click Developers. (This part of the web application is available only to users with the Administrator or Developer role and to the merchant owner.)

    Click Authorize Application, select My Website from the drop-down list, and click Authorize Application.

    Locate My Website in the Authorized Applications grid, and click Show Credentials to see your public key, secret keys, and account ID. You’ll need all three to create a charge through the AffiniPay Payment Gateway API

    Creating payment forms using hosted fields:

    AffiniPay hosted fields protect your payment page by tokenizing payment information. They provide SAQ-A PCI compliance, the highest level of PCI compliance. Hosted fields are <iframe> elements sourced from AffiniPay’s servers that contain a single corresponding <input> element. These iframes replace the input elements on your form that contain payment information.

    To create a payment page with hosted fields:

    1. Add a reference to the AffiniPay hosted fields JavaScript library
    2. Create a payment form
    3. Create a hosted fields configuration object
    4. Style the hosted fields
    5. Create a user-defined callback
    6. Initialize hosted fields
    7. Get a payment token

    Example page: eCheck payments:

    Results:

    • Make Echeck payment easily.
    • Increase productivity
    • Improve the customer experience

  • Mass Action Scheduler

    Mass Action Scheduler :-

    Mass Action Scheduler used to schedule Process Builder, Flows, Quick Actions, Email Alerts, Workflow Rules, or Apex to process records from Reports, List Views, SOQL, or Apex.

    No more waiting for records to be updated or creating clever workarounds to cause records to be updated to cause these actions to fire.

     

    Features:

    1. Declarative – no code necessary, never write Batch Apex again for queries that can be expressed in a report or list view and actions that can be expressed with a declarative alternative.
    2. On Platform – everything happens in Salesforce so no exporting or uploading data necessary.
    3. Timely – run actions manually or schedule hourly, daily, weekly, or any time in between.
    4. Versatile – explore the many data sources and actions that can be scheduled with Mass Action Scheduler.

    Almost any process automation you configure can be scheduled.

    Actions

    Supported Types

    Process Builder Processes that start when invoked by another process
    Flows Auto-launched flows (no screens).Any that can be called from Process Builder
    Quick Actions Create a Record, Update a Record, and Log a Call types
    Email Alerts All
    Workflow Rules All
    Apex Classes annotated with @InvocableMethod
     

    What can you do with a Mass Action Scheduler?

    • Run a process monthly, maybe to create a record or callout to an external system
    • Run data correction actions daily
    • Automatically add leads and contacts to campaigns based on report or list view criteria
    • Send emails on a periodic basis
    • Create “infinite” flows that continuously loop on a schedule
    • Perform field updates without exporting or importing data
     

    Steps:

    1. Create a new record under Mass Action Configurations.
    2. Add detailed information.
    3. Choose Source data to process.
    4. Choose an action to automate
    5. Map fields as inputs to selected action
    6. Choose how often to automate action
     

    Receive near real-time updates on batch job successes and failures like below.

    how to use Mass Action Scheduler with examples : https://github.com/douglascayers-org/sfdx-mass-action-scheduler/wiki/Examples

  • Companies are getting increasingly reliant on applications such as Salesforce.com and Google Drive. The ability to share information between these applications enables streamlining business processes. We can integrate Google API’s with salesforce by using below steps. Follow the below steps for the integration of Salesforce and Google drive :- Create App in Google Console Open […]

    Read More

  • What is Totango and Features Totango is the only independent customer success platform to manage customer relationships with complex account hierarchies and multiple products. Totango helps your organization deliver better business results in weeks. Not months. Spark – Totango Spark is the enterprise customer success solution designed to help your team achieve their goals. Actively […]

    Read More

  • How to choose which email integration is best for the company? Salesforce offers several products that integrate Salesforce with Microsoft or Google email or calendar applications It all depends upon your company requirements. There are several email integration available in the market but what suits the best depends on your business requirements. 1. If to Work […]

    Read More