> ## Documentation Index
> Fetch the complete documentation index at: /llms.txt
> Use this file to discover all available pages before exploring further.

# EIP-712

> Borrowers sign EIP-712 typed data for wallet proof, the agent grant, and repayment.

EIP-712 is how the borrower's wallet signs structured SohoPay messages. The agent does not use EIP-712 for the payment voucher. That voucher is Ed25519, covered in [Key management](/guides/key-management.md).

You will meet three borrower signatures:

| Message | When | Where it is signed |
| - | - | - |
| Wallet-proof challenge | The wallet is registered and still unproved | The borrower's wallet, after `request_signature_challenge` |
| `AgentAuthorizationGrant` | The borrower authorizes a terminal | The consent page at `consent_url` |
| Repayment authorization | The borrower pays the facility down | The repay consent page. The chain pull is [ERC-3009](/protocol/erc-3009.md). |

Each of these is a stop. Open the URL the API returned, or present the challenge the API returned. Do not retype the domain, the nonce, or the amounts into a message the borrower signs by hand, and do not ask them to paste the signature back into chat. The consent page submits the grant and the repayment.

The grant is the limit set: which merchants, how much per payment, and how much per period. [Policy](/protocol/policy-service.md) enforces it before a voucher is issued. Changing the grant means a new signature, not an edit from the agent.

Settlement batches are also EIP-712, signed by SohoPay's attestation key rather than the borrower. That signature is not part of your integration. See [Settlement attestation](/protocol/settlement-attestation.md).

## Next steps

> [card] [Borrower onboarding](/guides/borrower-onboarding.md)
>
> Where the first two signatures happen.

> [card] [Repayment](/guides/repayment.md)
>
> Where the third signature happens.
