SPAN Payment Flow with Flex Microform and Token Management System (TMS)
This document explains the span payment current flow and new flow with Cybersource, Flex Microform and, Token Management System.
Span Payment Current Flow: Without PCI DSS compliance
In the present flow of Span payments, the ETT application transmits billing information and credit card data to Span Payment API server. These details are sent to Cybersource “Simple order API” from the span Payment API server.
The Cybersource Simple Order API sends responses to the Span Payment API server. Finally the payment API server sends the response to the ETT Application.
SPAN Payment New Flow: With PCI DSS compliance – PCI SAQ A
In the Payment New flow,the Cybersource “Flex Microform” will be implemented in the ETT application.The Flex Microform will get credit card details and the ETT application will only save the billing information.
ETT Application, Flex Microform and Token Management System Process
New Credit Card Payment Flow
The ETT application, Flex microform and TMS integration flow is explained below.
The Flex microform generates the public key based on the RsaOaep256 algorithm and domain name.
The Flex microform generates the JWT token based on the Credit card information.
Finally, the ETT application creates a Payment request to the CyberSource REST API using JWT token and billing information. The CyberSource REST API sends responses to ETT Application.
Saved Credit Card Payment Flow
Here, the ETT application creates a Payment request to the CyberSource REST API using Customer Id and billing information. The CyberSource REST API sends responses to the ETT Application.
Create JWT Token using Flex Microform
Script: Create Card Number and CVV Field
After Adding Credit Card Details :
Script: Create Token and adding Expiry month and Expiry Year
Once the payment is success we will insert the payment log in payment transaction table
Stored Credit Card Details in Credit Card Profile table
TMS token types:
Four Token has store in our data base
Customer_Id: The customer token type represents data about the merchant's customer including email address, customer ID, shipping address (stored in a token), and other related fields
Payment_Instrument_Id: The payment instrument token type represents the complete billing details for the payment type including cardholder name, expiration date, and billing address.
Instrument_Identifier_Id: The instrument identifier token type represents the tokenized Primary Account Number (PAN) for card payments as well as the associated COF Network Token, or U.S. or Canadian bank account number and routing number
Payment_Response_Id: The payment Response id like payment Reference Id Each transaction have unique Payment_Response_Id. it use easily trace the transaction
Want to print your doc? This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (