PayNearMe for iGaming provides operators and players with a seamless, more reliable payment process for gaming. Our lightweight, mobile-first solution allows players to move money using any supported payment type, including credit and debit cards, ACH, cash, and mobile wallets like Apple Pay and Google Pay. PayNearMe's igaming solution supports three tiers of integration options: * Hosted Consumer Portals * Hosted Embedded Client * Full API Integration Hosted Consumer Portals provide a pre-built, turnkey solution to get cashier functionality up-and-running faster. It requires no development work and eliminates the Operator’s PCI compliance obligations and fraud liability. PayNearMe also provides Business Portals, where your Customer Service agents can make deposits on behalf of players, and Operators can track and generate reporting on deposits and withdrawals. For more information about Hosted Portals, contact your Sales representative. The Embedded Client leverages a drop-in payment form that captures player and payment type data to tokenize and/or complete a deposit/withdrawal. PayNearMe can customize the payment/withdrawal form to conform to the Operator’s specific branding standards so that the transition from the Operator’s site to PayNearMe and back is smooth and practically indiscernible. This solution can be integrated quickly with less development work than a full API integration. PayNearMe provides the Operator with a Javascript library that loads within an iframe and calls a snippet of JS to initiate the client form with the Operator’s preferred settings. A Full API Integration gives Operators the ability to customize their UI/UX and automate their workflows. As a more fluid and flexible method of service and information delivery, PayNearMe’s API provides Operators with an efficient way to update and distribute changes/enhancements. The API uses the same calls and callbacks as the embedded client but gives Operators full control of their cashier pages. # The Basics Before diving into integration details, you will need to understand some basic PayNearMe terminology and concepts. All PayNearMe merchants have a **site** with a **Site ID**. A site is simply a representation of your company. An Operator site is where players can initiate deposits and withdrawals. An ISV site is for gaming platform providers that manage the funds and wallet functionality for the Operator sites they service (also known as child sites). ISV sites can create Operator sites, which can then leverage PayNearMe services. To capture deposits and withdrawals, all Operator sites must have **orders**, which are represented by **Order IDs**. Think of orders like cage cashiers that facilitate the movement of funds to and from players. Every transaction is associated with a unique Order ID. Order amounts can vary but must be within business, regulatory, and, if applicable, player-defined limits. # Customizing PayNearMe for Your Business PayNearMe’s platform can be customized to meet the unique needs of your business operations. Use custom parameters to integrate with business-critical applications, create business rules, and keep players and your employees apprised of important data. Customized business rules automate your operations to solve complex business processes and reduce risk. ## Creating Custom Parameters All Operators track and maintain data unique to their players and business operations. PayNearMe’s default bulk file templates capture standard payment data but can also capture custom parameters that you configure. These custom parameters can then be used in API calls to third-party software integrations, player-facing interfaces like the Embedded Client and/or digital wallets or used in site-defined business and payment rules. Your PayNearMe Implementation Specialist will configure your custom parameters and add them to your Business Portal, and/or Agent Interface. To make this process more efficient, you can provide the following information about each parameter you want to configure: | Setting | Description | | :-------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Type | The following field types are supported:

Amount
Boolean
Date (MM/DD/YYYY)
Date/Time
Editable Amount (Displays an input box that can be edited)
Fixed Amount
Text

| | API Parameter Name | The API name of this parameter. Typically, this is made using the API parameter name in your system prefixed with `ext_` (e.g., if your system had a `bonus_code` parameter, PayNearMe would use `ext_bonus_code`). | | External Name | The field name of the API parameter in your system (i.e., the data field that this custom PayNearMe parameter will map to). | | Label | The label you want to display in the Business Portal and Embedded Client for this parameter. | | Require for `create_order`? | Indicates whether this parameter will be required for `create_order` API calls. | | Contains PII? | Indicates whether the value of this parameter contains Personal Identifying Information (PII). PayNearMe encrypts parameter values containing PII before storing. Encrypted parameters are only accessible to users with appropriate permissions. | | Validate-Only | Indicates whether you want to use this parameter only for account/player validation. Validation-only parameters are stored as hashed values. | | Show Row if Blank/Zero? | If this parameter is passed in as null or zero, do you want the field to display in the Embedded Client, Business Portal, and/or the Agent Interface? | | Include in Callbacks? | Do you want to include this parameter in any callbacks that are part of your business or payment flows? | | Format Hint? | Provides a format hint for Date/Time parameters | | Default Value | The default value for this parameter | | Minimum Value | Sets the minimum value allowed | | Maximum Value | Sets the maximum value allowed | | Mask Input Value? | Do you want PayNearMe to mask the input of this parameter before posting it to another server? This is recommended for parameters containing PII. | ## Customizing Business Rules PayNearMe’s business rules are logic-based if/then statements used to perform automated processes that support your unique business operations. These rules mitigate risk, reduce operating expenses, and decrease the time and expense involved with payment returns. You can choose from any of the following standard business rules: | Rule | Description | | :--------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Maximum Payment Amount | Defines the maximum amount allowed for an order or a player parameter. You can configure this rule to only apply to

players (i.e., agents can submit higher amounts),
electronic deposits (i.e., cash deposit amounts can be higher), and/or
ad-hoc deposits (i.e., Autopay deposit amounts can be higher).

| | Minimum Payment Amount | Defines the minimum amount allowed for an order or a player parameter. You can configure this rule to only apply to

players (i.e., agents can submit lower amounts),
electronic deposits (i.e., cash deposit amounts can be lower), and/or
ad-hoc deposits (i.e., Autopay deposit amounts can be lower).

| | Allowed NSF Returns Per Given Days | Defines the number of NSF returns allowed in a given number of days. PayNearMe will no longer allow ACH deposits for players who reach the NSF limit within the defined number of days (e.g., disallow ACH deposits if a player has 2 or more NSF returns in the previous 90 days). **NOTE:** Cash and card deposits will still be allowed. | | Check for Custom Parameter Value | If a custom parameter contains a defined value, the deposit will automatically decline (e.g., if `ext_at_max_reg_limit=true`, then decline deposit) This rule can be configured to only stop

player deposits (i.e., agents can still make deposit payments on behalf of the player)
electronic deposits (i.e., only cash deposits allowed)
ad-hoc deposits (i.e., Autopay deposits allowed)

| | Maximum Days in Future to Set AutoPay Schedule | Defines the maximum number of days in the future an Autopay schedule can start. | | Maximum Days in Future to Schedule Payment | Defines the maximum number of days in the future a one-time deposit can be scheduled. | | Payment Count Velocity | Defines the number of deposits that can be made in a given number of days. This can be configured for all deposits, just electronic deposits, or just player-made deposits. | | Payment Amount Velocity | Defines the total amount allowed for deposits within a given number of days. This amount can be a fixed value or equal to a custom parameter and can apply to all deposits, just electronic deposits, or just player-made deposits. | In addition to the standard business rules listed above, PayNearMe engineers can also create custom business rules that determine how, when, and if you should accept a deposit. For example, the following custom rules have been created for our merchants: * If the player has submitted a Stop Payment order on an ACH deposit, do not allow the player to make future ACH deposits. * Decline all future deposits if any deposit on the account is returned as unauthorized. For more information, consult your Implementation Specialist.