COUNTERPARTIES
Nobody should retype an IBAN for the third time this month. Your clients save beneficiaries and payers as counterparties, profile details plus one or more payout methods, and every repeat transfer starts prefilled, from the saved record, in a click.
A counterparty is more than a bank line: it is the profile, alias, account type, address, notes, holding one or more payout methods, each of a type the payment needs: SEPA, SWIFT, internal (another client of your platform) or local. The form adapts to the method, showing only the fields that rail requires, so a local payout and a SWIFT payout live side by side under one saved name, each ready to launch its own prefilled transfer.
Starting a payment from a saved payout method opens the matching transfer form, on-platform or external, with the counterparty’s stored data already in place. Repeat payments become a review-and-sign, not a data-entry task, and the transfer still passes every control the platform applies to money movement.
The counterparty workspace is built for a real payment operation: search by alias or name, sort by date, expand a record to see its linked payout methods, open full details. Full lifecycle control, create, edit, add or remove payout methods, delete with confirmation, and a built-in prompt keeps entered details to supported characters, catching a class of payment-processing errors before they happen.
Saved counterparty, prefilled form, PIN, sent, the whole point, demonstrated.