blockchyp 2.3.3 → 2.3.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a82102fd9132353d457d08fdaf7aabd9cb4c6392ddb515925f309c753fd21eef
-  data.tar.gz: '09186f6df35dd8fadfd87b4db9343f76cf4a53285b7dc2aea4b5a219ad27c41a'
+  metadata.gz: 42033eb64aa8814e7a85a87ada270bf68d53268dba82b84e0372515b5cfc0237
+  data.tar.gz: 01accfd7a693e15e97851cf23020788a62531a56a0644cfb8ded2eb0338c3bd6
 SHA512:
-  metadata.gz: 5af4709a88f893d915ece0dde84482ee60fa7595f874be3a546da99a721f114e3cb41927906b937c0c241db6f794f254bc28f4ff5933de3cd1577ac4ea518d98
-  data.tar.gz: fb1c3cd21d5af92e2c1c1cb010b20d7521ea0493c1d5e67140e4c4155570c5cf3638ebb08c81a50b024674c36b32354355241bf9d8752518d85ac3faa04a5913
+  metadata.gz: 13b0614fa9140e7695b587f7fb40624ef3cc45e1c33b0cee4d7247447a9a80f060fdb1d1c0d369f6e1c2c23dd6c6392a6d9df9f7b3010bc681420cbf6e726964
+  data.tar.gz: 6ffbec43dcdb35c8ba601d931ba44b56b50c4240430a91e0640816abbb20f5d72a8ed5cff0fdc34729c8b824cfb17cda7abc0f201f8774fd63309baf421ddd9d

data/README.md

@@ -679,23 +679,24 @@ more control over the look of the email message, you can omit the `autoSend`
 flag and send the customer email yourself.
 
 There are a lot of optional parameters for this API, but at a minimum
-you'll need to pass in a total, customer name, and email address.
+you'll need to pass in a total, customer name, and email address. (Unless
+you use the `cashier` flag.)
 
 **Customer Info**
 
-You must specify a customer, either by creating a new customer record inline
-or by passing in an existing Customer ID or Customer Ref.
+Unless you're using the `cashier` flag, you must specify a customer, either by
+creating a new customer record inline or by passing in an existing Customer ID or Customer Ref.
 
 **Line Item Level Data**
 
 It's not strictly required, but we strongly recommend sending line item level
-data with every request.  It will make the invoice look a little more complete
+detail with every request.  It will make the invoice look a little more complete
 and the data format for line item level data is the exact same format used
 for terminal line item display, so the same code can be used to support both areas.
 
 **Descriptions**
 
-You can also send a free form description or message that's displayed near
+You can also provide a free form description or message that's displayed near
 the bottom of the invoice.  Usually this is some kind of thank you note
 or instructions.
 
@@ -716,6 +717,16 @@ really just a safeguard to prevent real emails from going out when you may not e
 If you want BlockChyp to send the email for you, just add the `autoSend` flag with
 all requests.
 
+**Cashier Facing Card Entry**
+
+BlockChyp can be used to generate internal/cashier facing links as well.  This is
+designed for situations where you might need to take a phone order and you don't
+have a terminal.
+
+If you pass in the `cashier` flag, no email will be sent and you'll be be able to
+load the link in a browser or iframe for payment entry.  When the `cashier` flag
+is used, the `autoSend` flag will be ignored.
+
 **Payment Notifications**
 
 When a customer successfully submits payment, the merchant will receive an email

data/lib/blockchyp/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module BlockChyp
-  VERSION = '2.3.3'
+  VERSION = '2.3.4'
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: blockchyp
 version: !ruby/object:Gem::Version
-  version: 2.3.3
+  version: 2.3.4
 platform: ruby
 authors:
 - BlockChyp