Understanding the Platform
PayNearMe’s billing and payments platform encourages consumer self-service and on-time payments. As a fully customizable solution, you can control your UI/UX, payment channel/payment type acceptance, and business/payment flows through role- and rule-based management—without the lag time inherent in custom architectural and development updates. The platform can reduce or eliminate the burden of compliance certification through industry-leading security and encryption protocols, real-time consumer validations, and fraud analysis. Simplify bill presentment and payments using PayNearMe’s Engagements Engine, which gives you the ability to automate, tailor, and broaden your customer messaging.This portal provides an overview of PayNearMe’s platform, services, and features for both business leaders and developers. For information on how PayNearMe can accommodate your specific business needs, contact your sales or support representative.
Integrating with PayNearMe
As an all-in-one billing and payment solution, PayNearMe can accommodate different integration options, such as fully hosted checkout portals, embedded checkout solutions, or API-supported payment forms that give you complete control over the look and feel of your application or website. With support for multiple payment channels, payment types, and business flows, PayNearMe makes billing and payment acceptance easy, secure, and reliable.
Merchants have four methods for integrating to the PayNearMe platform: Fully Hosted, Embedded Form, Embedded Client, and Full API Integration.
Method | Description | Benefits |
---|---|---|
Fully Hosted | Pre-built Consumer and Business Portals that are hosted completely on PayNearMe servers. The Consumer portal gives consumers the ability to view and make ad-hoc payments, create a one-time-future schedule, or an AutoPay schedule. The Business Portal enables client agents (e.g., Customer Service) to accept payments on behalf of the consumer over the phone. |
|
Embedded Form | A PayNearMe-hosted form that clients can drop into their customer service interfaces. This enables client customer service agents to tokenize payment methods and make one-time payments on behalf of consumers without switching screens/windows. This solution allows clients to add payment processing to their internal applications without the compliance hassle. |
|
Embedded Client | A PayNearMe-hosted, drop-in payment form that can capture consumer and financial data for payments, disbursements, tokenization, or Autopay schedules. Each form is generated by invoking a PayNearMe native or web JS library initialized with a session-timed token and a client-customized script. Tokens include encrypted data values that authenticate genuine PayNearMe orders. Clients can define how many times consumers can access the form and for how long, and once accessed, how long the form will display until expiration. |
|
Full API Integration | A library of API calls that can integrate with client backend systems to create orders, add payment methods, make payments and disbursements, and create one-time-future schedules or AutoPay schedules. |
|
Understanding the PayNearMe Vernacular
Before diving into what PayNearMe can do for your business, you will need to understand some basic terminology and concepts used throughout the platform.
Term | Description |
---|---|
Order | To collect payments, all merchant sites must have orders. An order represents a consumer’s payment obligation to the merchant. This could be a monthly car payment, a required fine for a citation, or a deposit to an online gaming account. An order could be for a single purchase (e.g., the month’s rent payment) or for a standing balance that reduces over a series of transactions (e.g., a payment for a car loan). Orders are associated with individual consumers and settlement methods (the client bank account(s) where settlement and funding occur). Orders can be created via SFTP bulk file upload or individually through the API. |
Client | A Client is you, the lender, integrated service provider, igaming operator, property manager, or tolling agency that has contracted with PayNearMe for payment services. |
Consumer | Consumers are your customers or the borrowers, renters, players, or drivers who pay you to use your products and/or services. |
Callback | A server-side, HTTPS webhook notification sent by PayNearMe to a client to inform them of specific events that can occur during the transactions lifecycle (e.g., payments, chargebacks, returns, cancellations, etc.) |
PPA | A Payment Processor Account is a payment method used to make payments or collect disbursements (e.g., a credit card, debit card, bank, PayPal, Venmo, Cash App, Google Pay, or Apple Pay account). |
Push Order | A push order is used to track disbursement payments from a client to a consumer. This could be an online gaming payout, a loan disbursement, or an adjustment to an escrow overpayment. Push orders work like orders but require consumer identity validation, which PayNearMe performs through proprietary KYC and OFAC compliance checks. Push orders require clients to set up and fund For Benefit Of (FBO) accounts with one of PayNearMe's banking partners. For more information see the Disbursements section. |
Site | All PayNearMe clients have a site with a Site ID. A site is simply a representation of your company. A merchant site is where ad-hoc and scheduled payments can be initiated and captured by consumers. A partner or parent site is for independent software vendors or payment aggregators that facilitate payments for merchant payees they service (known as child sites). Parent sites can create child sites, which can then leverage PayNearMe services. |
Updated about 1 month ago