Platform / APIs and integration
Connect existing systems without losing transaction control.
Use authenticated interfaces and stable external references to connect meter, customer, payment, receipt and financial workflows to the systems your programme already operates.
Platform overview
Vend Utility provides defined integration boundaries between client systems, utility operations and financial orchestration so each service can exchange the context it needs without taking responsibility for another service’s outcome.
Relevant to
Disco technology teams
Enterprise architecture
Embedded payment channels
Systems integration partners
Inside the operating platform
See the work, states and evidence in one view.
This illustrative interface uses the fields and workflows already present across the Vend Power operating product.
Integration operations
API and event monitor
Search records
Programme recordsCurrent operating view
InterfaceOperationReferenceTimeResult
01Vend RESTResolve meter4500218831413:42:06200 OK
02CashbillInitiate Vend paymentVU-0421881313:42:08Accepted
03Vend GraphQLRead property remittalPROP-NG-02413:42:09200 OK
04Integration eventpayment.completed.v1VU-0421881313:42:14Delivered
Illustrative programme data · interface modelled on Vend Power operating workflows
What the platform controls
Operational capability with defined states and records.
01
Authenticated meter, customer, payment-history and receipt interfaces
02
Organisation-bound service credentials with scoped permissions
03
Stable external organisation, property and payment references
04
Dedicated Vend-to-Cashbill payment initiation and status interfaces
05
Controlled full-refund requests against the originating payment reference
06
Webhook, status-polling and event-driven workflow handoffs
07
Idempotent event consumption and transaction outbox delivery
Controlled workflow
How this capability moves.
Each stage leaves a distinct operating record so teams can identify where a transaction is and what must happen next.
Identify
Agree systems, service owners, data contracts, credentials and stable external references.
Connect
Integrate the required meter, customer, payment, receipt and event interfaces.
Validate
Test success, pending, retry, failure, refund and reconciliation scenarios.
Operate
Monitor requests and events against the same transaction evidence used by the platform.
Operating outcomes
What this makes possible.
Existing client channels can use one controlled transaction model
Utility and financial systems retain clear service boundaries
Retries and repeated events converge on one accepted outcome
Integration activity can be traced by reference, system and state