# 3.1 The Abyssal Bridge Engine (ABE) Logic The technical heart of AbyssPay is the **Abyssal Bridge Engine (ABE)**, a sophisticated settlement layer that manages the transition between non-custodial assets and fiat payment rails. Unlike traditional prepaid cards that require a manual "top-up" into a centralized pool, the ABE operates on a dynamic **Mapping & Liquidity Provision (MLP)** model. * **The Smart Escrow Layer:** When a user initiates a card session, the protocol interacts with a set of audited smart contracts on an L2 (e.g., Base or Arbitrum). The user locks their desired spending collateral (ETH, USDC, or USDT) into a non-custodial vault. * **The Virtual Credit Mapping:** The ABE generates a "Shadow Credit Limit" on the card rail, backed by the mathematical certainty of the locked on-chain assets. * **The Clearing House (Real-time Settlement):** When a swipe occurs, the ABE receives an authorization request from the merchant bank via a secure API. The engine immediately calculates the current oracle price of the collateral and releases the corresponding fiat amount through our licensed liquidity providers to settle the transaction in milliseconds. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.abysspay.xyz/chapter-3-the-abyssal-architecture-technical-clearing-and-settlement/3.1-the-abyssal-bridge-engine-abe-logic.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.