> ## Documentation Index > Fetch the complete documentation index at: https://docs.didit.me/llms.txt > Use this file to discover all available pages before exploring further. # 回复邮件提取 API：Travel Rule 邮件通道 > 通过一次性邮件提取链接接受或拒绝 Travel Rule 交易，并提供收款人姓名用于汇款人姓名比对。Didit 支持该流程。 响应“邮件取件 API”提示词 将提示词复制到剪贴板 \

\`Accept or decline a pending Travel Rule exchange from a one-time email pickup link - the counterparty-facing side of Didit's EMAIL fallback rail.

Endpoint:
POST https://verification.didit.me/v3/travel-rule/pickup/{token}/respond/

Authentication:
None - the one-time link token is the credential.

Request body (application/json):
\{"decision": "accept", "beneficiary_name": "Carlos Ruiz"}
or
\{"decision": "decline", "decline_reason": "not_our_customer"}

Optional fields:
\- ivms_response - your full IVMS 101 response (up to 16384 characters); its beneficiary name wins over beneficiary_name.
\- beneficiary_name - up to 255 characters.
\- decline_reason - data_mismatch | not_our_customer | wallet_not_hosted | sanctions | risk_appetite | jurisdiction | insufficient_data | other, or empty (the default) for no reason.
\- decline_detail - up to 512 characters; required when decision is decline and decline_reason is other.
\- contact - the contact the link was sent to, as a UUID; when the body leaves it out, the contact query parameter (the link's ?contact= value) is used.

Behavior:
\- accept - the beneficiary name is run through the originator's name rule: the transfer moves to COMPLETED on a match, COUNTERPARTY_MISMATCHED_DATA otherwise. Supply the name exactly as your records hold it. The response is {"status": "..."}.
\- decline - the transfer moves to COUNTERPARTY_VASP_GENERAL_DECLINE, and the sender's timeline records the reason. The response is {"status": "COUNTERPARTY_VASP_GENERAL_DECLINE", "decline_reason": "..."}.
\- You can answer once: afterwards both pickup endpoints return 410.

Failure modes:
\- 404 - unknown token.
\- 410 - the window closed: the counterparty already answered, the transfer left AWAITING_COUNTERPARTY, or the pickup deadline passed.
\- 400 - decision is missing or is not accept or decline, decline_detail is missing for a decline with reason other, ivms_response is not an IVMS 101 object or is too long, or a contact in the body is not a UUID ({"contact": ["Must be a valid UUID."]}).

Counterparty integration guide: /transaction-monitoring/travel-rule-interoperability#email-pickup.`

\
粘贴到 ## OpenAPI ````yaml zh/openapi-25.json POST /v3/travel-rule/pickup/{token}/respond/ openapi: 3.0.0 info: version: 3.0.0 title: Didit Verification API description: 身份证件验证 API。使用 x-api-key 请求头进行身份验证。 servers: - url: https://verification.didit.me security: [] tags: [] paths: /v3/travel-rule/pickup/{token}/respond/: post: tags: - Travel Rule summary: 响应邮件通道的提取请求 description: >- 公开且无需认证。通过邮件发送的提取链接接受或拒绝此次信息交换。接受时，将根据汇款人的 name_matching_strictness 策略对 beneficiary_name 进行比对核验。 operationId: respondTravelRulePickup parameters: - name: token in: path required: true schema: type: string - name: contact in: query required: false schema: type: string description: 链接的 `?contact=` 值。在请求体未发送 `contact` 时使用。 requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/TravelRulePickupRespondRequest' example: decision: accept beneficiary_name: Carlos Ruiz responses: '200': description: >- 最终的数据交换状态：接受后为 COMPLETED 或 COUNTERPARTY_MISMATCHED_DATA；拒绝后为 COUNTERPARTY_VASP_GENERAL_DECLINE，同时会原样返回 `decline_reason`。 content: application/json: schema: type: object properties: status: type: string decline_reason: type: string description: 在拒绝后提供。 examples: accepted: value: status: COMPLETED declined: value: status: COUNTERPARTY_VASP_GENERAL_DECLINE decline_reason: not_our_customer '400': description: >- 字段无效：例如缺少 `decision` 或其值不是 `accept` 或 `decline`、在 `decline_reason: other` 的拒绝操作中缺少 `decline_detail`、`ivms_response` 不是 IVMS 101 对象或长度超过 16384 个字符，或者请求体中的 `contact` 不是 UUID（`{"contact": ["Must be a valid UUID."]}`）。 content: application/json: example: decline_detail: - Say what the reason is when you choose another reason. '404': description: 未知的 token。 '410': description: 窗口已关闭：交易对手已回复、转账已脱离 AWAITING_COUNTERPARTY 状态，或已超过截止时间。 security: - {} x-codeSamples: - lang: curl label: curl source: >- curl -X POST https://verification.didit.me/v3/travel-rule/pickup/{token}/respond/ \ -H 'Content-Type: application/json' \ -d '{"decision": "accept", "beneficiary_name": "Carlos Ruiz"}' components: schemas: TravelRulePickupRespondRequest: type: object required: - decision properties: decision: type: string enum: - accept - decline beneficiary_name: type: string description: 您记录中保存的收款人姓名，已通过汇款方 VASP 的姓名规则处理。若 `ivms_response` 中指明了收款人，则以其为准。 maxLength: 255 decline_reason: type: string enum: - '' - data_mismatch - not_our_customer - wallet_not_hosted - sanctions - risk_appetite - jurisdiction - insufficient_data - other description: 您拒绝的原因。记录在发送方 VASP 的转账时间线上。如果您未提供原因，则为空（默认值）。 decline_detail: type: string maxLength: 512 description: 自由格式文本；当 `decision` 为 `decline` 且 `decline_reason` 为 `other` 时必填。 ivms_response: type: object description: 您完整的 IVMS 101 响应。其中的收款人姓名优先级高于 `beneficiary_name`。 contact: type: string format: uuid description: 链接发送到的联系人，取自链接的 `?contact=` 值。当请求体中省略时，使用 `contact` 查询参数。 ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.