# Approve a payment and retain its receipt

Resolve the recipient, review the exact payment, and recover the same attempt if its result is unknown.

Canonical: https://docs.bankeiz.com/payments/
Reviewed: 2026-10-25; coordinated packages 129.0.0; ruleset 127.0.0.

## Prepare the payment

1. **Open Send money** — Enter Amount to send and select the actual recipient. A supported username, payment request or QR helps locate that recipient.
2. **Add a note if useful** — The optional note is public in the Ledger and is limited to 280 characters. Keep private information out of it.
3. **Choose Review payment** — Inspect recipient, submitted dollars, quoted Phi, funding composition and displayed fee.
4. **Approve and send** — Use Send payment only after the actual request is correct. A link or conversation alone cannot approve spending.

## What the review binds

The existing Wallet path binds the recipient, amount and retained nonce. Supported funding uses Reserve first and Settlement for the remainder. The submitted dollar amount stays fixed while the Wallet computes execution Phi and funding composition. Account read access does not grant this financial approval, and an agent’s explanation does not replace the actual execution contract.

**Keep one intended payment through its result**

1. Prepare: Recipient, amount, note and nonce.
2. Review: Inspect the exact request.
3. Submit: One supported execution.
4. Resolve: Keep the original confirmed or terminal result.

## Read the result

**The result determines the next action**

| Display | Meaning | Next action |
| --- | --- | --- |
| Payment sent | The recorded result for the retained attempt has been accepted. | Inspect and save its record. |
| Payment not sent | A definitive refusal or terminal outcome is established. | Review the reason before another attempt. |
| Confirming your payment | The submitted outcome remains unknown. | Use Check payment outcome for the same nonce. |

## If funding is insufficient

The supported card-funded path can fund an established shortfall and then resume the original payment. It does not charge a card for an unknown submitted transfer. After card credit, transfer confirmation still has its own result. Back to send is an editing action; an already submitted charge or transfer must be resolved under its original reference.

- [Funding and card continuation](https://docs.bankeiz.com/funding/)

## Save and inspect the evidence

Use Save payment record where offered to export the retained Wallet response and transaction observation. That export preserves the observed result; it does not issue a new financial proof. Inspect the original financial evidence and participants through the supported history/receipt route. Keep the exact reference if the other party or support needs to locate the operation. A missing lookup remains unknown rather than permission to send again.

- [Receipts, history and attribution](https://docs.bankeiz.com/records/)
- [Exact recovery](https://docs.bankeiz.com/recovery/)

## Implementation sources

- [Send entry and recipient selection](https://github.com/kojibai/reality-grade-banking/blob/6c5d582/src/features/account/LivePayments.tsx)
- [Payment review and result controls](https://github.com/kojibai/reality-grade-banking/blob/6c5d582/src/features/account/WalletSendOperation.tsx)
- [Exact preparation, execution and nonce recovery](https://github.com/kojibai/reality-grade-banking/blob/6c5d582/src/receiz/wallet-send.ts)

## Related documentation

- [Receive by link, button or QR](https://docs.bankeiz.com/receiving/)
- [Fund the next operation](https://docs.bankeiz.com/funding/)
- [Inspect receipts, ownership and source history](https://docs.bankeiz.com/records/)
- [Recover the established operation](https://docs.bankeiz.com/recovery/)