LogoLogo
NymCardAPI catalogContact usnFront catalog
  • NYMCARD DOCUMENTATION
  • Get Started
    • nCore API Quick Tutorial
    • API Core Principles
    • Program management
      • Manage documents by APIs
      • User KYB process
      • Necessary parameters per user type
      • User ID verification by SDK
      • User KYC process
    • Issuance
      • Users
      • Cards
    • Issuing Physical Cards
      • Individual card issuance
      • Bulk card issuance
      • Card fulfillment
      • Card PIN management
      • Card replacement
      • Proxy number usage
    • Issuing Virtual Cards
      • Migration of virtual to physical card
    • Funding and transfers
      • Funding
      • Internal funding source
      • External funding source
        • From card
        • From bank account
        • Lean API flow
        • DAPI direct API flow
      • Transfers
      • Western Union APIs
    • Product Management
      • Card product
      • Balance limits
      • Velocity limits
      • Fees
      • Charges
      • Multi-currency
      • Authorization controls
        • Enhancements for MCC list management
    • Transactions
      • Payment ecosystem
      • Transaction lifecycle
      • Transaction types
      • Transaction endpoints scenarios
      • Multi-clearing process
    • Webhooks
      • Introduction to webhooks
      • nCore webhook events
      • Steps to configure a webhook
      • Webhooks samples
      • Webhook changes for simulation
      • Webhooks management
    • Security
      • PCI widget
      • 3D Secure
      • OTP SMS templates
    • Release announcements
      • Embedded Lending Release Notes
      • Changes in the release on 13/07/2023
      • Changes in the release on 23/05/2023
      • Changes in the release on 04/04/2023
  • For developers
    • nCore API catalog
    • nFront API catalog
Powered by GitBook
On this page

Was this helpful?

  1. Get Started
  2. Transactions

Transaction lifecycle

nCore platform creates and keeps electronic messages received from the payment card network as an object called transaction.

Transaction state changes during their lifecycle depends on whether they are in a temporary state or final state. Temporary and final transactions states are closely related to single-message and dual-message transactions.

In dual-message transaction system there are two or more transaction messages requires to complete, for example:

  • The merchant submits an electronic message containing the information required for an authorization decision at the time or purchase.

  • Later point in time, the merchant submits another electronic message containing additional data which is required for clearing and settlement.

In this scenario, the first message is a temporary transaction, which means it can be reversed. The last message is a final transaction.

Temporary transaction messages, such as authorizations flows in real time from the merchant to the issuer processor and these are handled synchronously. However, the final transaction messages are handled asynchronously because these requests can be submitted later.

Some transactions, for example a PIN based transactions contain all the information required for authorization and clearing in a single electronic message. These transactions are typically considered as final transactions that are handled synchronously.

PreviousPayment ecosystemNextTransaction types

Last updated 9 months ago

Was this helpful?