Our suite of stored value solutions makes it easy for developers to offer a featured-packed gift program. Integrating to Vantiv StoreCard automatically allows your merchants’ access to gift processing, Card Studio* and StoreCard. Developers can save development time and cost because we have built our gift platform around the core components that enable gift processing and value add services.
With Vantiv StoreCard, ISVs gain instant access to multi-store solutions with ACH funds transfers and cross-store reconciliation. New features and products for Vantiv StoreCard become available to ISVs with little or no development and implementation work.
There are ten supported gift transactions: Issue, Sale, NoNSFSale, Reload, Return, VoidIssue, VoidSale, VoidReload, VoidReturn and Balance. Although most developers choose to support the full range of gift transactions, at a minimum, we recommend supporting the following transactions at minimum for the best merchant and consumer experience possible:
Issue. Required to perform the initial activation and load of the card.
NoNSFSale. This transaction allows the merchant to deduct the remaining balance from a gift card even if the purchase amount is greater than the card balance. Using this transaction avoids the “insufficient funds” error that would normally be received.
Reload. Reload is used for monetary gift card loads. Return should be used for merchandise returns where the merchandise value is loaded onto a gift card.
Balance. Used to determine a gift card’s balance even if the card is deactivated or expired.
Void Issue. Reverses card activation.
Void Sale. Reverses a redemption without triggering daily reload limits.
Building Gift Transactions
There is a common set of data elements used to build gift transaction payloads, regardless of how your code is implemented. This section describes these common features as XML-based pairs.
The example below illustrates the XML data elements required by Vantiv StoreCard regardless of your integration method.
Note There are three data elements used to differentiate a gift transaction from a credit transaction: IpPort, TranType and the TranCode.
<?xml version="1.0"?> <TStream> <Transaction> <IpPort>9100</IpPort> <MerchantID>003503902913105</MerchantID> <TranType>PrePaid</TranType> <TranCode>Issue</TranCode> <InvoiceNo>123456</InvoiceNo> <RefNo>123456</RefNo> <Memo>POS.v123</Memo> <Account> <Track2>6050110010021825120=250110117</Track2> </Account> <Amount> <Purchase>250.00</Purchase> </Amount> </Transaction> </TStream>
Gift XML Response
All gift transactions return a common set of response data. This data contains authorization information and the available card balance and may be used to build receipts, build records for internal POS reporting, and can be stored for subsequent use.
The response data is divided into two sections:
<CmdResponse> summarizes the authorization. It shows the response origin, status of the authorization response (Approved, Declined, Success, Error) and clarification verbiage in the <TextResponse> .
<TranResponse> is the Transaction Response in detail.
<?xml version="1.0"?><RStream><CmdResponse><ResponseOrigin>Processor</ResponseOrigin><DSIXReturnCode>000000</DSIXReturnCode><CmdStatus>Approved</CmdStatus> <TextResponse>Approved</TextResponse> </CmdResponse><TranResponse><MerchantID>003503902913105</MerchantID><TranType>PrePaid</TranType><TranCode>Issue</TranCode><InvoiceNo>123456</InvoiceNo><OperatorID>test</OperatorID><AcctNo>6050110010021825120</AcctNo><RefNo>531747</RefNo> <AuthCode>531747</AuthCode><Amount><Authorize>250.00</Authorize> <Purchase>250.00</Purchase><Balance>250.00</Balance></Amount></TranResponse></RStream>
Card Encoding and Security Features
For fraud protection on Vantiv StoreCard generated gift cards, there is a printed set of numbers and an encoded set of numbers on the magnetic stripe. For manual entry, fraud protection is available using a three-digit card verification value (CVV). The three-digit security code is the standard encoding on gift cards.
Using the Card Verification Value (CVV)
CVVData is validated only when the gift card is used to tender a transaction (Sale, NoNSFSale, Reload, Return and corresponding voids.) “Non-tendered” transactions, Issue, VoidIssue and Balance, are not validated.
Gift cards are set to validate CVVData if supplied. If the CVVData tag is not provided, or if no value is present in the tag, the transaction is processed without any security check. If the CVVData tag is present and has data, our gift server will validate the data and return the appropriate result.
Developers must add a <CVVData> tag to the transaction request, which is used exclusively with the three-digit security code. The value is numeric, MIN 3 digits, MAX 4 digits
<TStream> <Transaction> <IpPort>9100</IpPort> <MerchantID>003503902913105</MerchantID> <TranType>PrePaid</TranType> <TranCode>Sale</TranCode> <InvoiceNo>123487</InvoiceNo> <RefNo>123487</RefNo> <Memo>POS.v345</Memo> <Account> <AcctNo>6050110000002570798</AcctNo> </Account> <Amount> <Purchase>3.52</Purchase> </Amount> <CVVData>880</CVVData> </Transaction> </TStream>
The result will be passed back as a single alpha character in the <CVVResult> tag in the response:
CmdStatus is Approved, CVVResult is M indicates an approved security code match: <CVVResult>M</CVVResult>
CmdStatus is Declined, CVVResult is P indicates and invalid, missing or incorrect security code:<CVVResult>P</CVVResult>
<RStream> <CmdResponse> <ResponseOrigin>Processor</ResponseOrigin> <DSIXReturnCode>000000</DSIXReturnCode> <CmdStatus>Approved</CmdStatus> <TextResponse>Approved</TextResponse> <UserTraceData></UserTraceData> </CmdResponse> <TranResponse> <MerchantID>003503902913105</MerchantID> <TranType>PrePaid</TranType> <TranCode>Sale</TranCode> <InvoiceNo>123487</InvoiceNo> <OperatorID>test</OperatorID> <AcctNo>6050110000002570798</AcctNo> <RefNo>532162</RefNo> <AuthCode>532162</AuthCode> <Amount> <Authorize>3.52</Authorize> <Purchase>3.52</Purchase> <Balance>193.48</Balance> </Amount> <CVVResult>M</CVVResult> </TranResponse> </RStream>
Transform a traditional gift card program into a complete stored value service—it maintains all the benefits of a gift card, with the enhanced capabilities of a rewards card and mobile payment card, all wrapped into one. . StoreCard is built on the gift platform, and is integrated in the exact same way as gift card processing. Developers who already support gift can use StoreCard with minimal changes to their payment solution, and their customers will then have easy access to all of the value added features.
Developers have the following options to enhance their store valued solution suite:
A website providing access to all features, letting consumers manage their cards. This site is customizable to match the merchant’s brand.
Cash Back Rewards
Designed to create customer loyalty, Cash Back Rewards encourage consumers to load and reload funds onto their cards. Every time a consumer uses their to make a purchase, the consumer receives a merchant-configured cash back reward added directly onto the card. Merchants determine the percentage consumers will receive.
Consumers have the option to convert their physical into a digital QR code representation of the card. They can then pay using their digital card from their smartphone. This requires a merchant to use a QR code scanner.
Using Manager, consumers can automatically or manually reload their at any time, by linking their card to their credit card.
Card Studio is an online, merchant branded website that is accessible from the Manager website. It can also be linked to the merchant’s website. It enables consumers to purchase physical or eGiftcards for friends and family.
Protect Your Card
Cardholders can register their cards online to guard against loss or theft. If their card is lost or stolen, cardholders can cancel their card and will send a new one loaded with the remaining balance.
Cardholders can view their transaction history from the Manager website.
This will enable cardholders to share, tweet or pin a virtual gift onto social media.
Merchants have the option to promote their business with digital from within their stores. Merchants determine the amount of the promotional offer and a text is sent to the customer with a link to open the digital .