Overview
Welcome to the Payment Connect Developer Guide.
This guide is intended for developers, technical consultants, architects, and implementation teams responsible for extending, customizing, integrating, and maintaining the technical components of the Payment Connect application.
The purpose of this documentation is to provide detailed technical guidance on the architecture, framework design, extensibility model, programmatic APIs, batch processes, data structures, and development standards used within the application.
This guide focuses on the technical implementation and development aspects of Payment Connect rather than administrative configuration or end-user functionality.
Intended Audience
This documentation is designed for:
|
Role |
Purpose |
|
Salesforce Developers |
Build and extend application functionality, including custom payment logic and programmatic triggers. |
|
Technical Architects |
Understand system architecture, security models (tokenization/encryption), and extensibility. |
|
Integration Developers |
Implement and manage external system integrations with payment gateways via APIs and webhooks. |
|
Implementation Teams |
Customize processing logic, data mappings, and workflow automation. |
|
Technical Consultants |
Support advanced business requirements and complex recurring billing logic. |
|
DevOps and Release Teams |
Manage deployments, metadata configurations, and environments. |
In This Guide
The Payment Connect Developer Guide is divided into specialized technical sections to help you integrate and extend the application seamlessly.
|
Child Guide |
What it covers |
|
Provides code samples, required parameters, and response structures for globally accessible Invocable methods and Apex wrapper classes. Covers how to programmatically automate ACH/Card requests, generate payment links, process saved methods, send outbound funds, and issue refunds via custom Apex or Salesforce Flows. |
|
|
Details the underlying data architecture required for building custom reporting, writing SOQL queries, and developing custom triggers. Includes a comprehensive Entity-Relationship Diagram (ERD) and object references for core objects like |