Prepare and track a banking service request

Start a request

The authenticated Banking requests area has a 12-step form: package, deployment, institution, network, governance, assets, fees, explorer, integrations, operations, add-ons and review. You can save a draft and return. New submissions use a short-lived account-bound token to avoid duplicates. Only the request owner can view or edit it.

1. Choose an orderable package and deployment mode.
2. Enter institution and project details currently known.
3. Save a draft if details are incomplete.

Describe requirements

Describe network name, symbol, chain ID, allocation, region, workload, validators and capacity; governance participants and controls; asset issuance and restrictions; fees; explorer branding; integrations; and operations for traffic, availability, backup, recovery, regions and support. Select catalogue add-ons. Enumerated choices, numbers, symbols and domains are validated. Do not enter credentials or private keys.

1. Complete relevant fields with concise intended requirements.
2. Select only applicable listed integrations and add-ons.
3. Review package, deployment, estimate and terms.

Estimate and submission purpose

The estimate is a planning preview, not contract, quote or payment request. Choose technical review, formal quote, order or demo. Submission requires valid configuration and terms acceptance and moves the request into review. A direct Pilot order can create a quote and service order in awaiting-payment state immediately; other purposes do not themselves mean a quote or implementation exists.

1. Choose the purpose that matches your actual request.
2. Accept terms and submit once from the review step.
3. Read the request status instead of relying on estimate.

Review a formal quote

After review, a formal quote may state setup and recurring terms, duration, agreement and expiry. The request page shows the quote and can download a configuration summary. Acceptance requires the agreement confirmation and matching quote identifier. The quote must be valid and unexpired with agreement terms present. Acceptance advances to approved; it is not payment confirmation or proof work started.

1. Read quote lines, setup, recurring amount and expiry.
2. Check the summary matches your submitted configuration.
3. Accept only the current quote and displayed agreement.

Pay and follow delivery

An approved order can proceed to awaiting payment and expose setup and recurring invoices. Pay through the invoice page and wait for payment confirmation. The request then moves separately through scheduled, in progress, delivered and completed states. Payment is a commercial event; implementation is operational work. The customer request page shows customer-visible events, not internal transition controls.

1. Open linked invoices and check amounts and due dates.
2. Pay through the invoice flow and verify confirmation.
3. Follow request events through schedule and delivery.

Edit and recover

Only drafts and requests marked requires information are editable. Correct requested fields, save and resubmit using the intended purpose. Repeating the same purpose for an already-submitted request returns its existing state; a different purpose or invalid state is rejected. Expired quotes cannot be accepted. Use the request workspace and support for the next permitted step.

1. Edit only while the request state permits it.
2. Correct named fields, save and resubmit as requested.
3. For expired quotes or later states, contact support.

Frequently asked questions

Related pages