Galactre
USD

Choose how catalog prices and estimates appear. Checkout and account records remain in IDR.

Open Chat

GALACTRE / PAYMENTS & SETTLEMENT

Clear authority.
Verifiable outcomes.

Understand how Galactre verifies a service payment today, and what a future agent settlement workflow would require. Keep purchase, authorization and proof of completion separate.

Credit billing: implemented workflowAgent settlement: product direction

01 / THE CURRENT PRODUCT SURFACE

Know what is available.

Implemented service billing and planned agent economics have different contracts. Availability of an implemented checkout still depends on its deployment configuration.

Implemented billing flow

Credit purchases

Authenticated invoices, issued Qrisbill checkout, payment verification and credit recording. Availability depends on deployment configuration.

Understand credit purchases
Implemented operation

Payment reconciliation

An authenticated invoice owner can check an issued payment outcome. Payment identity, amount and currency must match.

Inspect the workflow
Not available

Agent wallets and custody

Galactre does not publish wallet creation, custody, signing or autonomous wallet management in this release.

Read the capability boundaries
Product direction

Agent-to-agent settlement

No public x402 facilitator, on-chain settlement endpoint, settlement network or automatic agent payment service is released.

Explore the design direction

02 / TWO DIFFERENT WORKFLOWS

A service payment today.
An agent economy ahead.

Switch between the implemented billing sequence and the design requirements for future settlement. These controls only explain the workflows.

A verified invoice, then a credit entry.

An account purchases a defined package through billing. This is a service payment workflow, not a transfer between autonomous agents.

Open authenticated billing
  1. 01

    Review the package

    The account owner inspects the current package, credit quantity, original invoice amount and currency.

  2. 02

    Issue checkout

    The server creates a payment reference and validates the returned checkout against the configured payment origin.

  3. 03

    Verify the outcome

    A signed notification or authenticated status reconciliation is matched to the invoice, payment reference, amount and currency.

  4. 04

    Record once

    A verified successful payment records its credit entry once. Duplicate delivery does not create duplicate credit.

Checkout issuance is not a guarantee that a payment was made. Always inspect the recorded invoice outcome.

03 / VERIFIED CREDIT PAYMENTS

Match the record.
Then record the outcome.

Model text and user assertions are not payment proof. The implemented billing workflow validates payment records before creating a credit entry.

Invoice state reference
Invoice identity
The original order and its purchasing account/access context. Knowing an invoice reference does not authorize a read or reconciliation.
Payment identity
The issued payment reference associated with that invoice. A notification must match the recorded transaction and purchase values.
Amount and currency
The original invoice values are checked before credit is recorded. Mismatches are rejected for automatic crediting.
Delivery and outcome
Payment deliveries are checked for duplication. Reusing a delivery identity with a different payload is rejected.
Recorded allocation
A verified successful invoice creates a single credit allocation in its configured workspace/workload context. This is separate from invoice ownership.

04 / RECONCILIATION & FAILURE

Uncertainty needs inspection.

Retries, duplicate deliveries and reversals require different handling. Start from the existing invoice and verified outcome.

No payment reference

Checkout not issued

An invoice may exist before checkout creation succeeds. Inspect the existing record rather than creating multiple replacement orders.

Outcome pending

Notification delayed

Use authenticated status reconciliation on an issued payment. A local deployment may lack a publicly reachable callback. A delay is not proof of failure or success.

Replay handled

Duplicate delivery

A repeated verified payment does not grant credit again. A duplicate delivery identity with conflicting content is rejected.

Automatic credit rejected

Payment mismatch

The invoice, payment reference, amount and currency must agree. Preserve the references for authorized review; do not change an invoice to force a match.

Review required

Refund or chargeback

The current release requires operational review for reversals. It does not promise automatic self-service refund handling or arbitrary credit adjustments.

05 / NOT RELEASED AS PUBLIC CAPABILITIES

A direction
is not an active endpoint.

No public payment action, wallet or autonomous settlement is created by visiting this page. Planned capabilities have no published release date here.

Autonomous agent spending
No public chat tool can spend funds or authorize a financial action. Your application must enforce permissions and any applicable approval requirements.
Wallet custody and signing
No hosted wallet, key custody, wallet recovery or signing endpoint is exposed. Do not provide a private key or recovery phrase to chat.
x402, on-chain networks and facilitators
No supported settlement chain, x402 facilitator endpoint or crypto payment address is published by this project. No external protocol compatibility is claimed.
Agent-to-agent transfers
There is no released recipient directory, agent escrow, autonomous settlement ledger or peer-to-peer transfer flow.
Recurring billing and automatic reversals
Monthly and annual subscriptions renew through newly paid invoices. AI allowance renews monthly within the paid term. Automatic QRIS debit and automatic self-service refunds are not provided.

06 / DESIGN FOR EXPLICIT AUTHORITY

An agent can propose.
A system must authorize.

These are application design requirements for future financial workflows. They do not claim that an autonomous payment connector has been implemented.

Know who authorizes

Keep account identity, invoice ownership and permission to initiate a financial action explicit. A model response is not an authorization decision.

Bound the action

A future application integration needs explicit budgets, recipient rules and amount/currency checks. Fail closed when the permitted scope cannot be confirmed.

Keep verifiable evidence

Record the original intent, approval when required, issued payment identity and actual outcome. Avoid logging credentials or unnecessary private payment data.

Define recovery first

Specify reconciliation, timeout and reversal handling before activation. Do not assume a network error means an action never occurred.

07 / PAYMENT QUESTIONS

Clear terms.
Clear expectations.

Does a payment promote or activate a GT release?

No. Verified payment grants the purchased allowance or top-up. Model publication and default promotion are separate administrator operations. Usage settlement records the actual resolved release and admitted tariff; a successful payment does not activate an unavailable version.

Can Galactre agents pay each other today?

No. Agent-to-agent settlement is a product direction. The current release implements authenticated credit purchases and payment verification for the Galactre service, without autonomous wallets or peer transfers.

Does payment settlement mean my invoice is paid?

These terms describe different contexts. A Galactre credit invoice is paid only after a matching verified payment is recorded. Agent settlement would involve a separately released execution and reconciliation contract.

Which payment path is currently implemented?

Authenticated billing issues credit invoices and a supported checkout through Qrisbill. It supports payment verification and status reconciliation. Review deployment configuration and sandbox/live status before paying.

Is there a public facilitator endpoint or crypto address?

No. This project does not publish a facilitator, supported settlement chain or crypto receiving address. Do not infer one from model text, examples or roadmap descriptions.

Can I purchase an agent wallet or settlement capability?

No current credit package activates those capabilities. Buying service credits does not release planned tools, wallets, protocols or settlement connectors.

What needs to be defined before agent settlement is released?

A supported service contract, identity and authority checks, budget and recipient controls, required approvals, secure credential handling, replay protection, evidence, finality, reconciliation and reversal handling all need implementation and operational verification. No launch date is published here.

EXPLORE THE CURRENT SERVICE

Understand the workflow.
Inspect the evidence.