HYBRID DEVNET · PUBLIC EVIDENCE LIVEVerifiable infrastructure for value, markets, identity, and operational dataInspect the network

Products & integrations

How can we test an integration without moving real funds?

3 min read

Choose an agreed non-production environment and test discovery, permission boundaries, and failure handling before value-moving operations. Decision-only evaluations and read-only evidence checks can be useful where their documented scope fits the task.

Choose a test that cannot be mistaken for payment

Useful early tests include permitted reads, identity and scope checks, public evidence inspection, and decision-only evaluations where documented. They can demonstrate whether the application understands its inputs and results without requiring a financial action. Agree the exact environment and test data first. Do not assume that an endpoint is harmless simply because the interface looks like a preview; check whether the operation has side effects.

Test refusals and uncertainty as well as success

Try a request missing a required permission, an unsupported combination, or a delayed response within the agreed test plan. Confirm that the application explains the result and does not silently continue into another action. For an AI policy evaluation, test both allowed and denied proposals while retaining the decision-only boundary. For a wallet read, check that the interface does not claim activation from enrollment or current readiness from stale evidence.

Write down what the test established

Record the product, environment, operation, relevant configuration, expected result, and observed evidence. Keep examples of the denied cases as well as the successful one. Devnet credits and operational canaries should remain labeled as non-production or valueless evidence, not described as customer settlements. Use the results to decide what needs further review before a production phase. A safe pilot is valuable precisely because its limited scope is clear and can be repeated by another reviewer.

Illustrative example

Test an allowed and a denied AI proposal and retain the decision without constructing or broadcasting a payment.

In plain language

An example is not a production result

The examples in this FAQ explain how to think about a workflow. They are not reports of customer results, guarantees of performance, or instructions to use real funds. A useful evaluation starts with agreed access, a non-production environment where appropriate, and data that you are permitted to use. Decide in advance what a pass looks like and what must be refused. An allowed case alone is not enough: the team should also try an unauthorized request, a missing requirement, or an unavailable dependency where the test scope permits it. Keep the result and its context so someone else can understand what was demonstrated. Passing that test provides evidence for the tested combination of product, configuration, and environment. It does not automatically enable a different operation or network. Moving to production should be a separate, explicit decision with the required owners involved.

In plain language

What “enabled for your operation” means

A product can support several kinds of activity without making all of them available to every user. For example, reading an existing wallet record is different from creating a wallet, signing a transfer, or withdrawing to another chain. Access can depend on the account, environment, network, product configuration, and required approval. An operation is the exact action you want to take, such as reading a status or requesting a withdrawal. A scope is a limit on what a credential is allowed to request. Seeing a feature in documentation tells you what to investigate; it is not itself an access grant. During an evaluation, ask for a simple list of which actions are enabled, which are read-only, and which are outside the agreed test. Keep that list with your test results. This gives business users and developers the same understanding of what a successful demonstration actually establishes.

Conditions & limitations

A test result does not establish production readiness. Devnet credits and valueless infrastructure proofs are not real financial settlements.

What to do next

Agree the test data, environment, enabled operations, and evidence needed to pass the pilot.

First AI evaluation ↗Implementation guides ↗