Skip to main content

​
Implemented records

​
Transfer identity

A transfer is recorded once for every tracked wallet it affects. Deterministic uniqueness prevents replayed BSC logs or Solana observations from creating duplicates. BSC cursor identity includes the normalized wallet and token contract; it is not keyed only by a mutable symbol. Reference fields—payment_reference, settlement_reference, corridor_reference, origin/destination leg IDs, pairing method, confidence, and paired time—prepare indexed movement for future authoritative correlation.

​
Future records

The payment plane still needs versioned schemas for payment requests, quotes, acceptances, provider assignments, funding instructions, compliance decisions, Soroban network/contract identifiers, transaction submissions, contract events, payout evidence, disputes, refunds, and reconciliation outcomes. These records should be introduced through new migrations, never by rewriting historical migrations.