Once enabled by a DRB technician you will be able to configure:

 

Store & Forward Max Amount Per Transaction: (Dollars) - Transactions above this amount will be declined when offline and will not be Stored. Itis recommended this amount be set to the highest wash package or otherwise appropriate channel limit.

 

Store & Forward Max Time (Hours): - After expiration of this period, the device will decline transactions, and they will not be Stored.

• Representations and Acknowledgements.
  • By signing, Organization acknowledges and agrees: Organization has read and understands the S&F feature description, operational limits, and DRB help documentation regarding CardConnect/Fiserv Store and Forward. Organization is solely responsible for selecting appropriate configuration values and understands that incorrect settings may increase the risk of revenue loss or other adverse outcomes. Stored Transactions will be forwarded to the Processor only once, and any Forwarded Transaction declined by the Processor cannot be resubmitted by. Use of S&F function may result in additional charges, fines, assessments, or fees imposed by card brands, acquiring banks, or processors.  Organization accepts sole responsibility for such charges, fines, assessments, or fees. Organization remains responsible for compliance with applicable laws and industry standards, including PCI DSS requirements and any card brand regulations that apply to offline transaction capture and settlement.

 

• Fees and Charges.
  • Organization is responsible for any processing fees, chargebacks, penalties, or other costs associated with Stored or Forwarded Transactions, including those imposed by card brands, issuers, or processors.

 

• Indemnification.
  • To the fullest extent permitted by law, Organization shall indemnify, defend and hold harmless DRB and its affiliates, officers, directors, employees and agents from and against any and all claims, losses, liabilities, damages, costs and expenses (including reasonable attorneys’ fees) arising out of or relating to Organization’s use or misconfiguration of S&F, Stored or Forwarded Transactions, or Organization’s breach of this Agreement, except to the extent caused by DRB’s gross negligence or willful misconduct.

 

• Limitation of Liability Release.
  • Except for damages resulting from DRB’s gross negligence or willful misconduct, in no event shall DRB be liable for indirect, special, incidental, punitive or consequential damages, including without limitation loss of revenue, lost profits, or loss of data, arising from or related to S&F or this Agreement, even if DRB has been advised of the possibility of such damages. DRB’s total aggregate liability arising from or relating to S&F or this Agreement shall not exceed the greater of (a) the amount of fees paid by Organization to DRB for the use of S&F in the twelve (12) months preceding the claim, or (b) $500.

 

• Data Security and Privacy.
  • DRB will process cardholder data only in accordance with applicable law and the parties’ agreements. Organization is responsible for maintaining PCI DSS compliance and for ensuring that devices, endpoints, and merchant practices meet applicable security standards. Organization must promptly notify DRB of any suspected data breach involving Stored or Forwarded Transactions. Organization shall cooperate with DRB and any Processor in investigation and mitigation efforts. Organization acknowledges that offline storage increases certain security and fraud risks and accepts responsibility for mitigating those risks.

 

• Notices.
  • All notices under this Agreement must be in writing and delivered to DRB at KnowledgeCenter@drb.com or such other address as DRB may designate.

 

• Term and Termination.
  • This Agreement is effective as of the date signed by Organization and remains in effect until Organization requests deactivation of S&F or the parties terminate per their underlying service agreement. DRB may disable S&F immediately if required by card brand rules, Processor, or to protect payment integrity, or if Organization is in breach of this Agreement.

 

• Amendment.
  • This Agreement may be amended only by a written instrument signed by both parties. DRB may update configuration procedures or documentation and will notify Organization of material changes; continued use after notice constitutes acceptance of the changes. See Note below.

 

• Execution.
  • Organization certifies that the individual signing below is authorized to bind Organization to this Agreement.

• NOTE:
  • If Organization add a Site or removes a Site from this program, Organization must notify DRB, and additional documentation may be necessary to disable or enable Store & Forward.  Store & Forward may not be available on all Point-of-Sale devices.  Inquire of the Knowledge Center or your DRB contact as to which devices are in scope for this program.  

• Recitals.
  • DRB offers an optional Fiserv CardConnect EMV Store and Forward (“S&F”) feature that permits temporary offline storage of card transactions on an EMV reader when internet or device connectivity is unavailable.
  • S&F is a higher-risk feature that may increase the likelihood of transaction declines, chargebacks, processing fees, network association fines, or revenue loss. Accordingly, S&F is disabled by default and will be enabled only upon the Organization’s written authorization and acceptance of the terms of this Agreement.

 

• Definitions.
  • “Stored Transaction” means a transaction captured and retained on the EMV reader during an offline period for automatic forwarding to the processor when connectivity is restored.
  • “Forwarded Transaction” means a Stored Transaction that is submitted to the processor once connectivity is reestablished.
  • “Processor” means CardConnect/Fiserv or any payment processor engaged to process card transactions.

 

• Feature Description and Operational Limits.
  • S&F permits the capture and temporary storage of eligible payment transactions (including but not limited to single wash sales, gift cards, ARM, and tokenization transactions) on the originating EMV reader while connectivity is interrupted.
  • Only one (1) processing attempt will be made for each Stored Transaction. Any Forwarded Transaction that is declined by the Processor will not be able to be resubmitted.
  • Reconciliation of tokenization transactions will occur after the tokenization process completes.