Targets
Resolved destinations returned by the Bre-B central directory.
A target is what you get when you resolve a payment key against the Bre-B central directory: a structured object describing who owns the key, which bank holds the destination account, and what name will be displayed to the payer for confirmation. Targets are the artifact you pass to the outgoing-transfer endpoint when you want to dispatch a payment.
You will encounter targets every time your tenant sends a Bre-B payment. The flow is always: take a payment key, resolve it to a target, show the target's holder name to the payer for confirmation, then dispatch the transfer.
What a target contains
| Field | Meaning |
|---|---|
| Holder name | The name registered at the destination bank. Show this to the payer. |
| Holder document | Identification document of the holder (when authorized). |
| Destination participant | The institution that holds the destination account, returned as participant_nit and participant_name (null when Mono does not know the name yet). A Bre-B participant is not necessarily a bank. |
| Resolution timestamp | When the resolution happened. |
Pinning who should own the key
When you already know who must receive the money — a refund, for example — tell Mono who you expect behind the key when you resolve it. Send expected_creditor (document_type + document_number) to Resolve target, with any key format. Mono resolves the key only when the registered holder has that document. If someone else owns the key, the request fails with target_creditor_mismatch and no target is created, so a target_id obtained this way always points to the person you expected.
A transfer created with that target_id carries the same expected_creditor in its API response and webhooks, exactly as a transfer that sends expected_creditor with a key does. See Outgoing transfer use cases for both scenarios.