ScanTrack API.
Pay for results means results need to be tracked. For this reason Cardlesspay provides a very simple Scan Track API.
Closebys.com coupons can be scanned from two types of devices.
The mobile device that is connected to the Wireless network (or WIFI).
Regular barcode scanners that is connected to the Point of sale.
Mobile Wireless Device.
Since this is a pay for use system, the use of the coupon needs to be recorded in CloseBys network so that network owners can be paid.
Since the application bundled with the wireless device takes care reporting the use to the network, no additional work is required to be performed to track the use from CloseBys.
Note this mobile device will not communicate the use back to your point of sale system. In order to make it communicate your POS also needs to implement the ScanTrack API.
Once this API is implemented our mobile device can be configured to so that usage is tracked on your point of sale as well.
This usage count will be used to tally your receivables at the end of the day.
Note Small Mom and Pop Stores can choose not to do this extra work and rely on the reporting provided from the CloseBys itself.
Barcode Scanner:
If a merchant is using a barcode scanner connected to the Point of sale system then usage can be tracked on the internal systems and account can be tallied internally.
In order to update CloseBys the merchant POS needs to connect to CloseBys network to report the use.
This also helps CloseBys to know when the size for a particular promotion is reached and when to turn off the promotion.
Do the merchant Systems need to use the ScanTrack API to publish a promotion?.
Not required. Until the merchant implements the Scan Track API, the Pay per Clip method will be used to track usage.
<ScanTrackRequest>
<barcode>
<src> Business id as it is in the barcode</src>
<aid> Id of an item scanned from mywallet.<aid>
<id>id of an item scanned from Closebys.<id>
<iid> Internal identifier. Optional<iid>
<key> Customer identifier. Optional</key>
</barcode>
</ScanTrackRequest>
In addition Standard authentication header fields are required.
