RFP 26-26-214617 ARRC Electronic Payment Solution

ALASKA RAILROAD CORPORATION
327 W. Ship Creek Ave.
Anchorage, AK 99501
Phone 907-265-4467
HOPEM@AKRR.COM
July 23, 2026
REQUEST FOR PROPOSALS 26-26-214617
ARRC ELECTRONIC PAYMENT SOLUTION
Response Requested,
This form must be completed and returned to ensure receipt of future addenda or
additional information. Email this form to: Hopem@akrr.com. Addenda will be emailed to
the contact listed below; however, it is the responsibility of the offeror to make sure they
have received all addenda, and have acknowledged all addenda on their Proposal Bid
Form.
Firms that have not returned this cover sheet will not be informed of addenda and
will only be alerted to addenda by checking with the ARRC procurement officer or
by checking ARRC's internet site: www.alaskarailroad.com. Offerors must
acknowledge the receipt of all issued addendum on their Proposal Bid Form.
Company ______________________________________________________
Address ______________________________________________________
______________________________________________________
Contact ______________________________________________________
Phone ______________________________________________________
Email ______________________________________________________
Page 2

Alaska Railroad Corporation
327 W. Ship Creek Avenue, Anchorage, AK 99501
P.O. Box 107500, Anchorage, AK 99510-7500
Telephone 907.265.4467
July 23, 2026
REQUEST FOR PROPOSALS
The Alaska Railroad Corporation (ARRC) is soliciting proposals from interested offerors for the
following:
The Alaska Railroad Corporation ("ARRC") is soliciting proposals from qualified vendors to
provide, implement, integrate, and support a secure, customer-facing Accounts Receivable (AR)
Payment Portal solution fully integrated with Oracle JD Edwards EnterpriseOne (JDE E1).
26-26-214617
ARRC ELECTRONIC PAYMENT SOLUTION
IMPORTANT
Proposals will be received until 3:00 PM LOCAL TIME on Thursday, August 13, 2026 via
Dropbox.
One electronic copy of your firms Proposal must be submitted using Dropbox. Proposals shall be
submitted to the Dropbox link https://www.dropbox.com/request/ioejyywe56d6po8opjx5 by
proposal due date/time. It is the offeror's responsibility to verify with the Contract Administrator
that their proposal was received timely. If your firm has restrictions on Dropbox submittals, you
must contact your Contract Administrator at least seven days prior to the proposal due date to
discuss alternatives.
File naming convention shall be: Firm Name-RFP#-RFP Name
The original copy of your proposal will need to be mailed to the address provided below by the
proposal due date. This Original shall be fastened with one staple, binder clip, or rubber band. No
other form of binding shall be used and no cover or dividers shall be included. The Dropbox
submittal date/time will be used for the official receipt. Your proposal package (qualifications and
proposals) must be complete.
Alaska Railroad Corporation
Attn. Michele Hope, 2nd Floor
327 W. Ship Creek Avenue
Anchorage, Alaska 99501
Proposals received by email will not be considered for award. Proposals shall be submitted on
the forms furnished herein. Amendments or withdrawals must be received by ARRC's Contracts
Section via Dropbox prior to the date and time listed above.
Page 3

Pre-Proposal Conference: A pre-proposal conference will not be held. Send all questions to the
Contract Administrator.
The ARRC may award a contract resulting from this solicitation to the responsible offeror(s) whose
offer conformance to this solicitation will be most advantageous to the ARRC.
ARRC may reject any or all offers if such action is in the best interest of ARRC and waives
informalities and minor irregularities in offers received. ARRC may award a contract on the basis
of initial offers without discussion. Therefore, each initial offer should contain the offeror's best
terms from a technical standpoint. Any contract(s) resulting from this solicitation shall incorporate
ARRC's Standard Terms and Conditions contained in this solicitation package.
This Request for Proposals is not to be construed as a commitment of any kind nor does it commit
the ARRC to pay for any cost incurred in the submission of an offer or for any other cost incurred
prior to the execution of a formal contract.
Green Star recognizes organizations that demonstrate an ongoing commitment to
reducing waste, preventing pollution, and conserving energy. The railroad has repeatedly
recertified the Green Star Award and earned an additional Green Star Air
Quality Award in 2007. In 2011, Green Star Inc. presented the Alaska Railroad
with its premier new "Super Nova Award" recognizing a higher level of
leadership and commitment to doing business in an environmentally
responsible manner. ARRC continues to pursue programs and initiatives that promote
environmental stewardship.
Please direct all responses and/or questions concerning this Request for Proposals to Michele
Hope, Alaska Railroad Corporation, Supply Management, 327 Ship Creek Avenue, Anchorage,
AK 99501, telephone number (907) 265-4467. Email: HopeM@akrr.com
Page 4

SOLICITATION INDEX
SECTION A STATEMENT OF SERVICES
PROJECT TASK ORDER PROCESS
SECTION B PROPOSAL INFORMATION, CONDITIONS & INSTRUCTIONS
SECTION C PROPOSAL FORMAT AND CONTENT
SECTION D EVALUATION CRITERIA
SECTION E SELECTION PROCESS
SECTION F CONTRACTOR RESPONSIBILITY QUESTIONNAIRE & SERVICE BID FORM
SECTION G GENERAL TERMS & CONDITIONS
(PROFESSIONAL SERVICES CONTRACTS)
ATTACHMENTS:
Attachment 1 2025-2026 YTD Credit Card Sales
Attachment 2 Functional Requirements Response Matrix
This document can be downloaded from
https://www.dropbox.com/scl/fo/hhaizpm2r3g9dnsswmldr/AP8ArBnMPCNrg5Oriz
mztyg?rlkey=u9w8qo55omiq1jjjp6k5b43bu&st=l7fjiu00&dl=0
Page 5

SECTION A
STATEMENT OF SERVICES
1.0 INTRODUCTION
The Alaska Railroad Corporation ("ARRC") is soliciting proposals from qualified vendors to provide,
implement, integrate, and support a secure, customer-facing Accounts Receivable (AR) Payment
Portal solution fully integrated with Oracle JD Edwards EnterpriseOne (JDE E1).
1.1 Purpose
ARRC seeks a focused AR payment and invoice presentment solution specifically designed for and
proven in Oracle JD Edwards EnterpriseOne environments. The preferred solution shall specialize in:
* JD Edwards-integrated AR workflows
* Customer invoice presentment
* ACH and credit card payment processing
* Automated payment reconciliation
* Customer self-service account management
* PCI-compliant payment processing
* Direct/native JD Edwards integration
ARRC is not seeking a generalized eCommerce platform or broad customer engagement suite.
1.2 Background
ARRC is Alaska's statewide railroad, providing freight, passenger, real estate, and related business
services across a broad customer base. As part of these operations, ARRC manages a high volume
of customer billing and receivables activity that requires secure, accurate, and efficient payment
processing. ARRC is seeking a solution that supports customer self-service, improves payment
visibility and reconciliation, reduces manual effort, and integrates reliably with its existing Oracle JD
Edwards EnterpriseOne environment.
1.3 Current Environment and Existing Payment Processing Environment
ARRC currently utilizes on-premise Oracle JD Edwards EnterpriseOne on IBMi infrastructure utilizing
IBMi DB2 database as its enterprise resource planning (ERP) platform for finance and operational
processes.
ARRC currently utilizes Wells Fargo Merchant Services for payment processing. ARRC currently
processes credit card payments manually
2.0 SCOPE OF WORK
Under this contract, the selected contractor shall provide the software, implementation services,
technical expertise, documentation, training, and support necessary to deliver a secure, customer-
facing Electronic Payment Solution for ARRC. The contractor shall work collaboratively with ARRC
project staff throughout planning, configuration, integration, testing, deployment, and knowledge
transfer activities. The solution shall enable customers to view invoices and account balances, make
ACH and credit card payments, access payment history, and manage payment methods, while
Page 6

integrating with Oracle JD Edwards EnterpriseOne for customer, invoice, payment, and reconciliation
data. The contractor shall provide implementation guidance, system configuration, deployment
support, and post-go-live support necessary for ARRC to place the solution into operational use.
2.1 The solution shall modernize and streamline current customer payment operations through
implementation of a secure, PCI-compliant online payment portal that allows customers to:
* View open invoices and account balances
* Make ACH and credit card payments
* Access payment history and statements
* Manage payment methods
* Reduce manual AR processing effort
* Improve customer self-service capabilities
The solution must integrate directly with JD Edwards EnterpriseOne Accounts Receivable modules
and customer master data.
2.2 ARRC is open to alternative payment processors, gateways, or merchant service models
where vendors can demonstrate meaningful operational, technical, or financial advantages.
Vendors proposing alternative payment processing solutions shall clearly identify:
* expected transaction fee impacts or savings,
* gateway and processor licensing costs,
* migration requirements,
* reconciliation and settlement workflow impacts,
* PCI and security considerations,
* processor portability limitations,
* and any contractual or operational dependencies.
ARRC prefers solutions that preserve long-term flexibility and avoid unnecessary processor or
gateway lock-in.
2.3 Preferred Architecture Principles
ARRC strongly prefers solutions and implementation approaches that align with the following
architectural principles:
* Minimize middleware complexity and operational overhead
* Utilize native or direct Oracle JD Edwards EnterpriseOne integration methods wherever
possible
* Avoid duplicate customer, invoice, and payment repositories.
* Support real-time or near-real-time synchronization between the payment portal and JD
Edwards
* Minimize custom code ownership and long-term maintenance burden for ARRC
* Minimize PCI scope and exposure to ARRC systems, infrastructure, and personnel
* Utilize tokenized payment processing and secure hosted payment workflows
* Support future JD Edwards upgrades with minimal integration rework
* Provide strong auditability and reconciliation capabilities
* Support scalable SaaS or cloud-hosted deployment models
Page 7

* Provide resilient, supportable, and commercially mature architectures
* Reduce dependency on third-party integration platforms wherever feasible
* Support modern API-based integration approaches and/or JD Edwards Orchestrator
capabilities
* Provide clear operational ownership boundaries between vendor-managed and ARRC-
managed components
* Support maintainable and well-documented deployment architectures suitable for long-term
enterprise support
* Support Wells Fargo Merchant Services integration or provide alternative commercially
supported processor/gateway architecture
* Avoid proprietary payment processor lock-in that would limit ARRC's future flexibility
ARRC strongly prefers commercially mature solutions with proven production deployments in JD
Edwards EnterpriseOne environments on IBMi and IBMi DB2.
2.4 Out of Scope/ Non-Goals
ARRC is seeking a focused Electronic Payment Solution integrated with Oracle JD Edwards
EnterpriseOne. The following initiatives are considered outside the scope of this procurement unless
explicitly proposed as optional services:
* Full eCommerce platform replacement
* Customer Relationship Management (CRM) replacement
* Retail point-of-sale (POS) systems
* General customer portal modernization unrelated to AR workflows
* ERP replacement or ERP modernization initiatives
* Custom application development unrelated to payment processing
* Large-scale digital commerce transformation initiatives
3 SCHEDULE
Project Start 8/19/2026
Project Completion 11/1/2026
4 CONTRACT PERIOD OF PERFORMANCE
The contract will be effective upon execution and will remain in force for an initial term of two (2)
years, with up to three (3) additional one (1) year renewal options that may be exercised by ARRC at
its sole discretion and upon mutual agreement of the parties. Due to the nature of ARRC's operational
and system integration needs, ARRC may, if the solution proves successful and continues to meet
ARRC's requirements, establish the selected solution as its long-term standard and continue its use
for up to ten (10) years before evaluating replacement or alternative solutions. Any continuation
beyond the initial term and renewal options would be subject to ARRC's procurement requirements,
funding availability, satisfactory contractor performance, and execution of any required future
agreement documentation. This contract shall remain subject to ARRC's Cancellation/Termination
provisions set forth in Section G, including ARRC's right to cancel the contract for convenience or
terminate for default in accordance with those terms.
Page 8

5. Cybersecurity Requirement
All cybersecurity practices shall comply with applicable federal, state, and ARRC policies, including
any standards if incorporated in the solicitation or subsequent task orders.
6. Data Protection and Handling
The Contractor shall protect all ARRC data, including confidential, sensitive, and personally
identifiable information, against unauthorized access, disclosure, alteration, and destruction.
Contractor shall ensure that such data is collected, stored, transmitted, and disposed of in a secure
manner. The Contractor may be held liable for costs, damages, or remedial actions resulting from
cybersecurity incidents caused by the Contractor's failure to comply with the requirements of this
clause.
Page 9

SECTION B
PROPOSAL INFORMATION, CONDITIONS & INSTRUCTIONS
1. Pre-Submission Proposal Inquires
Offerors shall promptly notify ARRC of any ambiguity, inconsistency, conflict, or error which they may
discover upon examination of the solicitation documents. Verbal inquiries regarding this RFP are not
permitted. All inquiries must be made in writing and received at ARRC's offices 10 days prior to
submission deadline. Written inquiries must be submitted to Michele Hope hopem@akrr.com.
ARRC will respond to all or part of the written inquiries received through the issuance of a written
Addendum to the RFP, if in the opinion of ARRC, such information is deemed necessary to submit
proposals or if the lack of it would be prejudicial to other prospective Offerors. Oral and all other non-
written responses, interpretations and clarifications shall not be legally effective or binding. Any Offeror
who attempts to use or uses any means or method other than those set forth above to communicate
with ARRC or any director, officer, employee or agent thereof, regarding this RFP shall be subject to
disqualification.
2. Proposal Submission Deadline
Proposals will be received until 3:00 PM LOCAL TIME on Thursday, August 13, 2026 via Dropbox.
One electronic copy of your firms Proposal must be submitted using Dropbox. Proposals shall be
submitted to the Dropbox link https://www.dropbox.com/request/ioejyywe56d6po8opjx5 by
proposal due date/time. It is the offeror's responsibility to verify with the Contract Administrator that their
proposal was received timely. If your firm has restrictions on Dropbox submittals, you must contact your
Contract Administrator at least seven days prior to the proposal due date to discuss alternatives.
File naming convention shall be: Firm Name-RFP#-RFPName
The original copy of your proposal will need to be mailed to the address provided below by the proposal
due date. This Original shall be fastened with one staple, binder clip, or rubber band. No other form of
binding shall be used and no cover or dividers shall be included. The Dropbox submittal date/time will
be used for the official receipt. Your proposal package (qualifications and proposals) must be complete.
Alaska Railroad Corporation
Attn. Michele Hope,
327 W. Ship Creek Avenue
Anchorage, Alaska 99501
Proposals received by email will not be considered for award. Proposals shall be submitted on the forms
furnished herein. Amendments or withdrawals must be received by ARRC's Contracts Section via
Dropbox prior to the date and time listed above.
Proposals received after the time and date set forth above shall be rejected. All proposals submitted in
response to this solicitation must be signed by an individual with the legal authority to submit the offer
on behalf of the company.
Page 10