Partners, messages, and reconciliation, on one interface desk
MeetCarbon Cloud interconnection interface management keeps partners, the protocol catalog, joint debugging, four-way messages, and reconciliation gaps on one ledger. Inbound status and order messages can be searched. Failed outbound pushes sit in a retry queue. Charging orders, chargers, and invoices stay in charging operations. Lot orders stay in smart parking. Device models stay in IoT.
- Catalog
- Public, business, trade, and filing
- Four ways
- Push in, call in, call out, push out
- Debugging
- Inbound, outbound, and signing tools
- Gaps
- A gap is not marked settled
- They push38%
- They call22%
- We call24%
- We push16%
- Star Charge push waiting to retryRetry
- Yesterday’s order messages differGap
From a partner to a reconciliation gap
A partner and the catalog come first. Debugging follows. Messages land in the center. Reconciliation only marks gaps. Observability and scene extensions read the same ledger.
- 01
Add a partner
Register the operator or platform, turn on the interfaces you need, and set a rate limit.
Partners - 02
Match the catalog
Check public, business, trade, credentials, extensions, and regulatory filing as separate layers.
Protocol catalog - 03
Debug both ways
The wizard, inbound bench, and outbound bench prove one sample. The signing tool is for joint debugging only.
Onboarding - 04
Messages enter the center
They push, they call, we call, and we push are searched separately. Failed pushes enter the queue.
Message center - 05
See the gaps
Order and bill messages are compared with platform orders. A gap stays listed and is not marked settled.
Trade and reconciliation - 06
Observe and extend
Availability and alerts show whether an interface is stable. Station open, filing, and two-wheel protocols sit in scene extensions.
Observe · scenes
Walk the connection lifecycle
The workbench is the hero. The eight items below cover the catalog, partners, dictionaries, debugging, messages, observability, reconciliation, and scene extensions.
Protocol catalog
Catalog and partnersInterfaces are grouped by the standard layers. The catalog says what each layer covers. Switches are turned on during onboarding.
- Six layers stay separate, including regulatory filing
- Each layer states what it covers
- Switches are still configured on the partner
Message counts and gap counts on the sample cards explain the layout. They are not a partner’s settlement result.
Partners, messages, and reconciliation each keep their own marks
A disabled partner stops answering. A failed signature and a pending retry are not marked successful. A reconciliation gap is not marked settled.
Partner
Whether this platform can send and receive now.
- Benches and samples onlyIn debuggingDebugging
- Opened interfaces can send and receiveLiveLive
- No answers and no pushesDisabledDisabled
Message
How far this message has gone.
- Stored after sign and decrypt succeedSignature passedPassed
- Not marked receivedSignature failedFailed
- A failed push stays in the queueRetry pendingRetry
Reconciliation
Whether the message matches the platform order.
- Order and bill messages line upMatchedMatched
- The difference is listed and not marked settledGapGap
8 statesSwitches, rate limits, and keys live on the partner profile. Whether money arrived follows charging operations and the payment channel.
Access, debugging, duty, reconciliation, and filing each open a different page
One interface ledger. Someone owns partners, someone runs samples, someone watches messages, someone checks gaps.
How many are live, who is still in debugging, and which interfaces are still off?
- Live partners on the workbench
- Partner state
- Interface switches
Read the workbench, run debugging, then mark the gap
One connection starts on the workbench and ends with an alert or a filing record. Every step can return to the partner and the message.
- 1Read the workbench
Live partners and the to-handle list decide whether to drill in.
- 2Match the catalog
Confirm the layer exists, then turn it on for the partner.
- 3Run debugging
Prove one inbound sample and one outbound sample on the benches.
- 4Collect messages
Search by direction. Failed signatures and retries stay apart.
- 5Mark the gap
Order messages that do not match are listed on their own.
- 6Alert or file
Raise an availability alert, or keep a regulatory filing record.
The interface ledger stays here
Partners, the catalog, debugging, messages, reconciliation gaps, and scene extensions stay in interconnection interface management. Orders, devices, and money have their own products.
This product owns
- Protocol catalog and dictionaries
- Partner profiles, switches, and rate limits
- Wizard, inbound bench, outbound bench, and signing tools
- Four-way messages and the push queue
- Order and bill messages, and reconciliation gaps
- Availability, alerts, station open, regulatory filing, and two-wheel protocols
Neighboring products own
- Charging operationsViewCharging orders, chargers, tariffs, and invoices. This page keeps interconnection messages and gaps.
- Smart parkingViewLot orders, fees, and monthly passes. A station can be opened in a scene. Tariffs are not edited here.
- IoT device managementViewThing models and protocols such as MQTT. Partner HTTP interconnection stays in this product.
Fund transfer, wallet credits, and official regulatory receipts are not completed on this page. A reconciliation gap only means the message and the platform order do not match. It does not mean money was received or refunded.
Five steps to connect one partner
Create the profile and the switches, prove inbound and outbound on the benches, then messages can be searched and reconciliation can show a gap.
- 1Partner name, endpoint, and keys
- 2The interface list to turn on
- 3One station or order you can sample
- 4The platform-order range reconciliation should compare
Debug samples do not enter formal reconciliation. A message that fails signature check is not marked received.
- 1Create the partner
Enter the operator or platform and leave the state in debugging.
Done when · Profile opens - 2Turn switches on
Select interfaces from the catalog and set a rate limit.
Done when · Switches saved - 3Prove inbound and outbound
Run one sample on each bench. The signing tool only assists debugging.
Done when · Samples replay - 4Messages are searchable
All four directions and the push queue can be filtered by partner.
Done when · Center has a record - 5Reconciliation shows a gap
Compare one platform order with its message and list the difference on its own.
Done when · Gap opens
Many partners, a trail, and export
The same interface desk is split by partner. Switches, rate limits, messages, and filings keep a record. Deployment and price are on the pricing page.
Each operator or platform has its own profile, switches, and rate limit.
Call rate sits on the partner. Signing and crypto tools serve debugging.
Messages, signature results, retries, and filings keep a record.
Export messages and reconciliation gaps by partner and time.
Turned on per project, on the same account system as MeetCarbon charging and parking.
When keys and messages must stay on the customer network, the platform can run there.
Car interconnection, two-wheel, filing, and station open all land on this ledger
The main path is partners and messages. Scene extensions cover station open, regulatory filing, and two-wheel protocols.
Messages, orders, and device protocols
These five points are what teams check before going live.
How does this split from charging operations?
Charging orders, chargers, tariffs, and invoices stay in charging operations. This page keeps partner messages, the push queue, and reconciliation gaps. The two can be matched by order id. They are not one bill.
How does this split from IoT?
Thing models and device protocols such as MQTT stay in IoT. This page is HTTP interconnection with operators and platforms: the catalog, signing, messages, and reconciliation gaps.
Does a reconciliation gap mean money was received?
A gap only means the message and the platform order do not match. Received or refunded status follows charging operations and the payment channel. This page does not mark a gap as settled.
Does a regulatory filing mean the authority received it?
This page keeps the pack and the submission record. Whether the authority received it, and whether a receipt exists, follows their system. Without a receipt it is not marked passed.
Can the signing tool replace the partner’s production environment?
Signing and crypto tools only serve debug samples. Production send and receive use interfaces a live partner has opened. Sample messages do not enter formal reconciliation.
Lay out send and receive for one partner
Tell us which platform it is, which interfaces to open, and whether regulatory filing is in scope. We will walk the catalog, debugging, messages, and reconciliation gaps for that scope.