11 docs tagged with "Payment Processing"

In this integration mode, Open Fabric converts network events into ledger operations (debit/credit/hold/release) and calls your backend via API to apply them. You do not need to download or process clearing files.

Open Fabric forwards real-time authorization messages to your backend for an approval/decline decision. These requests must be handled in sub-second time to avoid network timeouts and customer-facing declines.

Clearing is the process where the network requests funds movement for previously-authorized transactions. Clearing is provided in batches (multiple times per day).

Attach the documents that support the dispute before you submit it. Documents can only be added, replaced, or removed while the dispute is in draft. They become immutable the moment you submit.

A chargeback is the dispute process of the card networks. When your customer contests a transaction (an unauthorized charge, goods that never arrived, a refund that was never credited) and the issue cannot be resolved with the merchant directly, you raise a chargeback against the acquirer through the card network.

Overview

Create a draft dispute against the transaction your customer contests. Nothing is sent to the card network yet, so you can still edit the dispute or add evidence before submitting it.

In this integration mode, you integrate closer to the card network lifecycle.

The network may reverse a previously-approved authorization (for example, due to timeout/technical failure, or a merchant reversal). When Open Fabric receives these events, we forward them to you as reversal notifications.

Settlement is where the network settles net amounts between your settlement account(s) and the network. Settlement is typically generated once per day per settlement account / currency.

Once the evidence checklist is satisfied, file the dispute with the card network. From here the evidence is locked and the case proceeds on the network's timeline.