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.
- Payment Pages
- Quick Bill
- Scheduled Payments
- Comprehensive Reporting
- Custom Dashboard
- Scheduled Payments
- Integrated Partners
- Integrate Payments into Your Website
1: Configure your partner OAuth application
- 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.)
- 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:
- Create a payment form
- Create a hosted fields configuration object
- Style the hosted fields
- Create a user-defined callback
- Initialize hosted fields
- Get a payment token
Example page: eCheck payments:
- Make Echeck payment easily.
- Increase productivity
- Improve the customer experience