Start from the right business record
Place the payment action beside the customer, invoice, account, or other record your team is already handling.
Put ACH inside the business system your team already uses.
Initiate a supported payment from the relevant customer, invoice, or account; keep its transaction identifier and status with the business record; void it when supported; and bring returns, corrections, batch details, and acknowledgements into a reviewable flow.
Your operational result
Your team can handle supported ACH activity without copying transaction details between your application, email, spreadsheets, and a separate reconciliation process.
SolutionACH actions inside your business application
FoundationKotapay Cashier for Laravel
Verified supportInitiate, retrieve, check, void, and report
Your ACH flow
Give each payment a clear path from initiation to reconciliation.
FoleyBridge builds the screens, records, rules, and Kotapay connection around the way your team accepts and reviews supported ACH activity.
Validate before submission
Check the required bank-account, amount, effective-date, and identifying values before sending a supported request to Kotapay.
Retain the transaction details
Keep the submitted amount, effective date, transaction identifier, related business record, and available status together.
Check payment status
Retrieve the status supported by the gateway and show it where your team reviews the related customer or transaction.
Control supported voids
Let an authorized user request a supported void by transaction identifier and preserve the result with the payment record.
Review reconciliation activity
Bring supported return, correction, processed-batch, and file-acknowledgement reports into queues or reports your team can act on.
Operational records
Keep the payment event connected to the business event.
Your application can preserve the context your team needs to answer what was submitted, what Kotapay returned, and what needs attention next.
Amount, date, and identifier
Store the submitted values and gateway transaction identifier with the customer, invoice, or account that initiated the payment.
A compatible payment-method record
Use the package’s bank-account model and supported stored-method flow without exposing full bank details in ordinary application screens or logs.
The latest supported gateway state
Show the available status, the time it was checked, and any application action that followed.
Failures your team can resolve
Turn validation and supported gateway exceptions into clear messages, retry rules, or queues instead of silent failures.
Items that require attention
Present supported report details alongside the related records so your team can investigate and update its own systems.
Evidence of file processing
Retrieve the supported processed-batch and file-acknowledgement details required by your reconciliation routine.
Built around your operation
Connect Kotapay to the records and controls you already rely on.
Your team sees a business flow, not a collection of raw gateway calls.
Show us the payment trigger
Identify where the amount, customer, bank method, effective date, and authorization originate in your current system.
Map each supported action
Define when your application initiates, retrieves, checks, or voids a payment and which reports your team must review.
Build the screens and controls
Add validation, user permissions, transaction records, status displays, exception handling, and reconciliation views around the integration.
Test the real operating cases
Verify representative submissions, retrievals, status checks, supported voids, failures, returns, corrections, batches, and acknowledgements.
Existing engineering
Kotapay Cashier provides a public Laravel foundation.
The MIT-licensed package shows the gateway layer FoleyBridge has already implemented: a Laravel service provider, ACH billing trait, payment and bank-account models, gateway services, validation, events, and exceptions.
- Create a supported ACH payment
- Retrieve a payment or the collection exposed by the service
- Check the supported status of a submitted payment
- Request a supported void by transaction identifier
- Submit a charge using a compatible stored payment method
- Retrieve supported return, correction, processed-batch, and file-acknowledgement reports
Package requirements: PHP 8.1 or newer, supported Laravel 10, 11, or 12 components, a valid Kotapay account, and the gateway access required by your application.
Before launch
Prepare the controls around the gateway connection.
- Confirm the payment types, effective dates, limits, and reports supported by your Kotapay account.
- Define who can initiate, review, and void supported payments inside your application.
- Document customer authorization, notice, return, correction, and record-retention requirements.
- Protect bank details, gateway credentials, application logs, and administrative access.
- Test representative payments, failures, supported voids, returns, corrections, and reconciliation cases.
Kotapay Cashier is an integration layer. It does not provide a bank account, guarantee transaction acceptance, set gateway fees, or replace the legal and operational controls required for ACH payments.
Custom ACH integration
Describe the ACH flow you want inside your system.
Tell us where a payment starts, which records it belongs to, who handles exceptions, and which reconciliation reports your team needs.