Deprecated — use POST /v1/tenant/international/payouts instead.
This endpoint exposes the provider-specific (Uniteller / More) request
shape and is retained only for backward compatibility with integrations
that shipped against it before the provider abstraction landed. New
integrations MUST use the clean /payouts endpoint above, which
accepts only Finogates-domain identifiers and resolves provider context
internally.
Accepts two shapes (see MorePayoutRequest):
product_id + payee_payment_method_id): goes through
the standard Tenant -> User -> PaymentMethod flow with ledger reservation
and provider routing.beneficiary + bankInfo): preserved for the
previously shipped integration; bypasses entitlement checks and ledger
escrow.Documentation Index
Fetch the complete documentation index at: https://developer.finogates.com/llms.txt
Use this file to discover all available pages before exploring further.
The access token received from the authorization server in the OAuth 2.0 flow.
(Legacy) UUID of the bank payment method used
Request body for POST /tenant/international/payouts/process.
Sender is server-managed. API consumers never need to supply sender /
business-identity fields. Finogates resolves the sender block from the
SUA-configured platform defaults (Tenant.meta['uniteller_sender_defaults'])
and injects it into the outbound provider call. This is part of the
Finogates orchestration contract — provider-specific mandatory fields are
enriched server-side, never required from the customer.
The endpoint accepts two shapes:
product_id + payee_payment_method_id.
Routes through ensure_tenant_product_entitled → select_provider
→ reserve_funds → ensure_payment_method_binding → provider call
→ move_escrow_to_clearing / release_escrow. Beneficiary and bank
info are loaded from the saved PaymentMethod (and optionally a
linked InternationalBeneficiary).beneficiary + bankInfo.
Bypasses the entitlement / ledger / binding pipeline. New integrations
MUST use the canonical shape; the legacy shape is retained only to
avoid breaking the integration that just shipped.Exactly one of the two shapes must be present.
Internal/advanced fields (not part of the public surface, retained for backward compatibility):
sender_id — explicitly select a saved InternationalSender row
instead of falling back to the platform defaults. Tenant-managed by SUA;
most integrators leave this unset.sender — inline override of the sender block. Deprecated and
ignored by default: server-side enrichment runs whenever the
enrichment dispatcher returns a populated block, so this field is
effectively only honored when the platform has no defaults configured.3233(Internal) Explicit saved-sender override. Leave unset to use platform defaults.
(Deprecated) Inline sender override. Server-side enrichment from platform defaults takes precedence.