Skip to content

Business Portal

Manage pay-ins, payouts, settlement and reporting in one portal.

Pay-ins, payouts, treasury, reports and configuration in one secure web portal — with role-based access, double-signature approvals and sign-in protected by a one-time code.

Log in to Business PortalContact sales
  • Email, password and one-time code
  • Built-in and custom roles
  • Double-signature payouts
Modules in one portal
7
Built-in roles, plus your own
Custom roles
A second user approves each payout before it is sent
Double-signature approval
One-time verification code at sign-in
Email code

Modules

Your whole operation, in seven modules

Each module covers one part of your payment operation, and roles decide who can see and do what in each of them.

  • Overview

    Key metrics and transaction search at a glance, in dark or light mode.

  • Reports

    Balance, projected balance, activity, transaction detail and historical reports, exportable to XLS.

  • Payins

    WebCheckout requests and payment links, manual refunds, refund review and chargeback handling.

  • Payouts

    Single and batch payouts, review and double-signature approval, cancellation and proof of payment.

  • Settlement & Exchange

    Currency exchange, internal transfers, Wire In and Wire Out, and payment accounts for bank accounts and stablecoin wallets.

  • Configurations

    Users and roles, webhooks and notifications, IP and BIN allow-listing, low-balance alerts and reference lists.

  • Operations

    Real-time system status and incident updates.

A closer look

How teams use the Business Portal

Pay one beneficiary or thousands

Send a single payout or upload a batch file. Payouts that require approval wait for a second authorized user before any money moves.

  • Batch payouts from a file
  • Review and double-signature approval
  • Cancel before a payout is in progress
  • Download the proof of payment
Explore payouts

Payouts with approvals

Double-signature approval on payouts

Double signature separates the person who prepares a payout from the person who approves it.

  1. Prepare

    An operator creates a single payout or uploads a batch file in the payout module.

  2. Approve

    The payout waits in Pending authorization until a second authorized user approves it.

  3. Send

    The amount is locked from your balance and the transfer goes out on the local rail.

  4. Confirm

    The status updates in the portal and by webhook. Download the proof of payment when it completes.

Security

Secure by default

The portal is built around the controls finance and security teams expect: strong sign-in, least-privilege roles and separation of duties for every movement of money.

  • Sign-in with email, password and a one-time verification code
  • Built-in and custom roles, with least-privilege guidance
  • Double-signature approvals for payouts
  • IP allow-listing for API calls, managed in the portal
  • HMAC-signed webhooks and activity logs
Security at Localpayment

For every team

One portal, the right access for each team

  • Finance

    Reports, balances and XLS exports for daily reconciliation.

  • Operations

    Payouts, refunds and chargebacks, with approvals built in.

  • Treasury

    FX, internal transfers and Wire In or Wire Out across countries.

  • Administrators

    Users, roles, webhooks and IP allow-listing in one place.

Capabilities

What you can do in the portal — and through the API

Every operation has a counterpart for your systems, so teams and integrations see the same data.

  • Pay-ins

    In the Business Portal
    Search, refund and export collections; create payment links and WebCheckout requests
    Through the API
    POST /api/payin/, refunds, GET transaction status

  • Payouts

    In the Business Portal
    Individual and batch payouts, double-signature approvals, proofs of payment
    Through the API
    POST /api/payout/ with requireAuth, authorize, cancel

  • Treasury

    In the Business Portal
    Balances, projected balance, FX, internal transfers, Wire In / Wire Out
    Through the API
    Balance, activity and balance-reconciliation endpoints

  • Reports

    In the Business Portal
    Balance, projected balance, activity, transaction detail, notifications; XLS export
    Through the API
    List and filter transactions with pagination

  • Settings

    In the Business Portal
    Users and roles, API credentials, webhook URLs, IP allow-listing
    Through the API
    POST /api/token/ for JWT access and refresh tokens

  • Environments

    In the Business Portal
    Stage and production portals with separate credentials
    Through the API
    api.stage.localpayment.com and api.v3.localpayment.com

Module availability depends on the products enabled for your account.

For developers

Everything in the portal is also an API call

Operations teams work in the portal; your systems read the same statuses through the REST API. Here, a transaction status lookup by your own externalId.

  • Same externalId in the portal, webhooks and API
  • Bearer token from POST /api/token/
  • Illustrative values — identifiers are fictitious
Reporting & reconciliation guide
# Get a JWT (never hardcode credentials)
curl -X POST https://api.stage.localpayment.com/api/token/ \
  -H "Content-Type: application/json" \
  -d '{ "username": "<api-user>", "password": "<from-your-secrets-manager>" }'

# Look up a transaction by your externalId
curl https://api.stage.localpayment.com/api/transactions/7c1e2f7a-0000-4000-8000-000000000042/status \
  -H "Authorization: Bearer $ACCESS_TOKEN"

Use cases

One portal for every operating model

Frequently asked questions

How do I get access to the Business Portal?

Access is set up during onboarding. Once your users are created, they sign in on the Business Portal login page with their email, password and a one-time code.

How does sign-in work?

Users enter their email and password, then a one-time verification code sent to their email address.

Can I control what each user can see and do?

Yes. Assign built-in roles or create custom ones, and follow the least-privilege guidance so each person has only the permissions they need.

Can I require two approvals before a payout is sent?

Yes. With double signature, a payout waits in Pending authorization until a second authorized user approves it, in the portal or through the API.

Can I send payouts in bulk?

Yes. Upload a batch file in the payout module. Batch payouts follow the same approvals, statuses and proofs of payment as individual payouts.

Is there a test environment?

Yes. Stage mirrors production with no real money, with its own portal and API credentials, issued at the start of the partnership.

Can I export data for my accounting system?

Yes. Most reports can be exported to XLS, and the same data is available through the balance, activity and transaction APIs for automated imports.

Can I restrict access to specific IP addresses?

Yes. Administrators can allow-list the IP addresses permitted to use the API credentials, in addition to roles, MFA on sign-in and double signature on payouts.

Also on the same API

Already a customer?

Log in to the Business Portal. New to Localpayment? Talk to our team to get your access set up.

Sign inContact sales

How can we help?

Download your copy

Leave your details and get the full edition instantly.