Versions Compared

Version Old Version 73 New Version Current
Changes made by

Miles Graves

Miles Graves

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

All integrating Partners and software platforms work with the Payrix Solution Engineers and Sales Team to create a Scope of Work (SOW) that describes what your integration will look like and the associated requirements across the Payrix Platform.

During Pre-Implementation, you will work with a Payrix Solution Engineer to fill in the Partner Pre-Integration Form. This page includes details about all of the information that you will need to provide on the form.

Table of Contents

Table of Contents
minLevel1
maxLevel1

...

Building a Scope of Work with our Prospect Platforms involves a discussion about Features and Risk Considerations and collects data on how our Clients hope to leverage the Payrix Platform across the 4 four Merchant Support features related to Payment Facilitation:

...

Ahead of your SOW call:

The following steps will be required ahead of creating the SOW:

...

  1. We collect the information defined below to determine the best options for your business.

  2. Click Next after all information is entered.

Question

Description

Notes

Select a product line: 

Pro or Premium

Completed by Payrix*

Processor:

Worldpay or Fiserv

Completed by Payrix*

Partner/PF’s Legal Name:

Partner Legal Name

Completed by Payrix*

Partner/PF DBA(s)

Partner Business Name

Completed by Payrix*

Partner URL:

Partner URL

Completed by Payrix*

Payrix Contacts

Question

Description

Sales Executive:

Name of Sales Executive

Implementations Manager:

Name of Implementations Manager

Solutions Engineer:

Name of Solutions Engineer

Relationship Manager:

Name of Assigned Relationship Manager

Partner Contacts

  1. Enter Partner Contact Full Name, Role, Email, and Phone.

  2. Click Add Contact and then click Next.

...

  1. Select your target markets.

  2. Use the free form to let us know how your clients receive payments and then click Next.

Question

Note

What industries or verticals are your target markets?

  • Field Service Management

  • Clothing Boutique

  • Education / Healthcare

  • eCommerce

  • Non-Profit/Associations / Church Management

  • Food Truck

  • Membership Management

  • Billing / Invoicing / Messaging

  • FSR Advance

  • Registration / Scheduling

  • FSR Lite

  • Janitorial / Maid

  • Restaurant

  • Gymnasium

  • Medical / Legal / Dental / Vet

  • Healthcare

  • Appointment-Based (Salon-Spa)

  • Hotel / Leisure

  • Auto Shop Contractors

  • Liquor Store

  • Pet Store

  • Convenient Store / Deli / Grocery

  • Professional Services

  • QSR

  • Simple (SMB) Retail

How do your clients take payments today?

Brief description explaining how your clients accept payments today.

Example: “A practice management solution for dental offices that focuses on accepting payments through text to pay...”

What are your goals and objectives for the user experience?

Examples:

  • “My merchant currently uses my software for invoicing.”

  • “We’re generating a link that is sent to the patient. They open it, enter password gated information (last name and DOB that has to match the practice database) and then access a URL where the can submit payment.”

Processing Capabilities

  1. Select Yes or No to let us know whether you need Card Present Integration. If Yes, proceed to Card Present Integration. If No, proceed to Card Not Present.

  2. Enter your Card Present Volume percentage.

...

  1. Select the countries where your merchants are located.

  2. Add the Percentage.

  3. Click Add Country to add more than one country and then click Next.

Info

Payrix currently operates in the United States, Canada, Australia, and New Zealand.

Partner Development Details

  1. Select your development platform.

  2. Use the free form to provide details about your current application and then click Next.

Question

Note

Development language

For Example:

  • Ruby

  • cURL

  • C#

Development platform

Will you be bringing on 3rd party developers?

Yes or No

Do you have a payment technical resource on staff?

Yes or No

Developer company name

Name

Business registration number of the developer

BRN of developer

Developer website

URL

...

Merchant Onboarding Details

...

  1. Select Yes or No to let us know whether you require a White Label.

  2. If you selected Yes, select any applicable White Label Options.

  3. Select your Merchant Boarding Integration. (See the Board Integration Options table for an explanation of each option.)

  4. Click Next.

Boarding Integration Options

Note

Portal (manual signup)

Clients will be boarded via the Payrix portal.

Signup Forms

Merchants will be boarded via an online signup form.

Full API Boarding

The Full Boarding API is a managed service allowing you

to

complete flexibility in the creation of

a

new merchant

location(s)

locations.

Bulk-boarding

Payrix will work with you to meet the necessary technical and underwriting requirements for bulk onboarding, simplifying the process of migrating your existing Merchants to Payrix from another platform.

Payment Workflow

  1. Select all applicable Payment Workflow Options.

  2. Use the free form to describe your ideal payment workflow and then click Next.

Question

Note

Payment Methods

Please describe your ideal payment workflow:

Example:

  • Customer visits your website, selects products, clicks “pay now”.

  • The customer enters payment information to pay for the product.

  • Payment is approved, and the customer is given the option to save card details  for future payments.

  • The product is dispatched.

Merchant Pricing Strategy

  1. Select all applicable Merchant Pricing Options.

  2. Select all applicable Merchant Pricing Types.

  3. Use the free form to describe your go-to-market pricing strategy for payments and then click Next.

Fees

Question

Note

Resource

How are fees assigned to the merchant?

  • Managed via Groups for Merchants (API or Portal)

  • Setup on each Merchant Individually (API or Portal)

  • Submitted with the Transaction (API)

Fees and Fee Models within Payrix


Can you describe how do bill fees to your clients?

Handled internally or via portal?

Funding/Disbursement Integration

  1. Select all applicable Merchant Funding Options.

  2. Use the free form to describe how you currently fund and send payouts to your clients and then click Next.

Question

Note

Resource

Portal Only

Funding is managed via the portal

/wiki/spaces/PE/pages/936903129

Settlement & Funding

API Integration (payout schedule)

Funding managed by Partner/Client

...

Risk and Compliance

Disputes and Chargebacks

  1. Select all applicable Chargeback Management Options.

  2. Use the free form to describe how you currently manage your chargeback process and then click Next.

Question

Note

/wiki/spaces/PAL/pages/733347878

Disputes are managed via the portal

API Integration (chargeback documents/responses)

Disputes are managed by Partner/Client via API

How do you manage the chargeback process? Please describe below?

Provide brief descriptions.

Example: Chargeback are managed by a third party

Current System

Question

Note

Describe your current application and what it does:

For example:

  • A B2B system facilitating payments for customers with regular fees?

  • An eCommerce site with a shopping cart using WordPress or similar?

Reporting Integration

Question

Note

Portal Only

Reports are managed via the portal

Payrix API

Reports are pulled by Partner/Client via API

Scheduled Reports

Scheduled reports created and generated by Payrix

What type of reporting do you utilize today, and how do you provide reporting to your clients?

Example:

  • Reconciliation Reports

  • Transaction Research

  • User Log

Data Migration (Token Transfer)

Question

Note

Data Migration Required:

Yes or No

Direct:

Partner owns tokens

Current Processor:

Example:

  • First Data

  • Elavon

  • TSYS

  • WorldPay

Number of Tokens Under Migration:

How many tokens do we need to transfer

Migration Target Date:

Expected date to complete token migration

Outline Migration Plan:

Token Migration Process (import into Payrix)

...

Partner/PF Launch Timeline

Projected Timeline

Question

Description

Implementation Kick-Off Call:

Date of first implementation call

Anticipated Integration Target Start Date:

When do you expect to start the integration

Anticipated Integration Target Finish Date:

Expected date to finalize integration

Target Beta Onboarded:

Estimated Target Beta Onboarded Date

Target Full Launch:

Target full launch date