Skip to main content

Agentic Payment

Agentic Payment manages store-scoped payment provider instances and crypto wallets used by approved commerce or procurement workflows.

Payment Provider Instances​

The overview reports active instances, total registered instances, and the primary payment method. A store can install provider templates from Marketplace and configure each resulting instance separately.

Use a primary provider only when the intended default behavior is understood. Other installed providers can remain available for explicit workflows without becoming the default.

Crypto Wallets​

The Crypto Wallet area connects wallets that can approve USDC supplier payments from the selected store. Wallet access should be treated as a high-risk capability even when a flow only prepares a payment request.

  1. Open Marketplace and select a payment provider template.
  2. Register the provider for the selected store.
  3. Store credentials through the approved configuration surface.
  4. Test the provider in a non-production environment.
  5. Enable the instance.
  6. Set it as primary only when default routing is intended.
  7. Monitor failures and rotate credentials according to policy.
  1. Confirm the store and payment purpose.
  2. Connect the approved wallet.
  3. Validate network, currency, address, and authorization ownership.
  4. Use a low-value test transaction where permitted.
  5. Require the appropriate approval before supplier payment.
  6. Reconcile the transaction with the procurement order.

Usage Scenarios​

  • Maintain multiple payment providers and select one primary gateway.
  • Pilot a new provider without replacing the current default.
  • Attach payment capability to an Agentic Commerce flow.
  • Approve a USDC supplier payment from a procurement order.
  • Disable a compromised provider instance while keeping alternatives available.

Security Controls​

  • Never place provider secrets or wallet recovery material in documentation, prompts, or logs.
  • Separate payment preparation from approval when required.
  • Validate amount, currency, destination, and order ownership.
  • Apply passkey or another supported strong approval control.
  • Use least-privilege service credentials.
  • Reconcile provider status with the authoritative payment record.
  • Disable and rotate compromised configurations immediately.