CC swipe and data flow

Can someone tell me if this is the way cc info flows?

A customer gets their card swiped at a terminal, the credit card info goes to the DB via REST first then to payment gateway server if it needs to be authorized and processed.

Parents
  • Hi John!

    The basic process is as follows:

    1. The Client sends an Authorizations request to the Payment Gateway Service (PGS)
    2. PGS communicates with the Gateway for sale request and approval
    3. PGS adds a row to T_CC_SERVER_LOG with authorization response from Gateway
    If successful,
    1. Client executes AP_STORE_ACCOUNT_DATA and adds credit card details to T_ACCOUNT_DATA, if default setting CC_STORE_ACCOUNT=Yes
    2. Client adds row to T_PAYMENT
    3. Client communicates success to PGS
    4. PGS adds a row to T_CC_SERVER_LOG
    5. PGS returns successful response code to Client

    Hope this helps!

    Nick

  • What about the initial scan? I see the cc info populate in the record, which I assume means that info has made it's way into the DB. Am I correct?

Reply Children
No Data