Skip to content

For authorised financial institutions · Confidential under NDA when exchanged

Safeguarding interface

Segregation and partner-core operations

Perper is a technology layer. Customer funds, safeguarding, settlement and redemption remain with the authorised institution. This page describes the APIs the SDK portal exposes so your core can receive hold / release / settle / redeem / top-up instructions — without Perper acting as EMI issuer.

Hard rule

  • Safeguarding procedures never credit or debit Contabo /user/balance as if Perper were the issuer.
  • Ops stay blocked until partner fiat rails are live (legal name + CBCG register) and your partner core endpoint is configured.
  • When allowed, the portal forwards each op to your core’s safeguarding endpoint; failures are recorded in the host audit trail.

Operations

  • top_up

    Notify partner core that safeguarded funds increased for a subject.

  • hold

    Request a reservation on segregated funds (e.g. pending settlement).

  • release

    Release a prior hold without settlement.

  • settle

    Settle against a hold / payment obligation on the partner ledger.

  • redeem

    Redeem / payout path against the institution’s safeguarding model.

Daily reconciliation

  • Signed-in merchants can request a reconciliation report (ISO day) from the portal Balance page.
  • The report shows whether partner rails and core are ready, optional partner safeguarded balance when available, delta, and a status of not configured / awaiting partner / balanced / mismatch.
  • Portal Contabo balance is labelled as operational UX only — not the EMI safeguarding ledger.

Current gate

…