blockchyp 2.8.1 → 2.9.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6ca7677d78c85630b93fb9bf78d789bfe1b725cce8308479081a7976150f7501
-  data.tar.gz: d28a5450a9160b30660c15ecb42b96edd9234b5e6340d2d783063747b9d18826
+  metadata.gz: 3f0071c666888b2819dceede378f34e8ac289a93c5bce2558a9fb96c6ab9db6d
+  data.tar.gz: 2720946c145f85bd87020318b4c023bc4af71305124710950aefe9861ec4546a
 SHA512:
-  metadata.gz: 543efe438e6fa01ad95cec127f3d029838e9e6436385ed39332c29690921838daafa0605a9a808d2bf4800e2a8952bd4b1c72af535b8543921a893de02137b5b
-  data.tar.gz: 8c7cff2a427c0019351fb4714efe104b383c4f48f74a09138fd005205922a33d759e9c64bbdfb4da64d99cf0ef5169a5bf75e758f30cd7960802440afddd3fb0
+  metadata.gz: d5d3c98b1eb28598bf10bd6fa695e1b5cf5e799594727b689ccfad5e00200b0a6b93e2116cc44cd723630b22d28dd23ea0a514a556b19f98a4b47de648dfd6e0
+  data.tar.gz: dc93fbf9313fad01a2b42f2b309c427eb1b3d2f9fd5247e34e65c3e1d4d4d4fdbb3e8c921c828604baa87305fead56e87d5d964b6155928d557a86648a69b3ec

data/README.md

@@ -135,20 +135,20 @@ property instead.
 
 **Card Numbers and Mag Stripes**
 
-You can also pass in PANs and Mag Stripes, but you probably shouldn't.  This will
+You can also pass in PANs and Mag Stripes, but you probably shouldn't. This will
 put you in PCI scope and the most common vector for POS breaches is key logging.
 If you use terminals for manual card entry, you'll bypass any key loggers that
 might be maliciously running on the point-of-sale system.
 
 **Common Variations**
 
-* **Gift Card Redemption**:  There's no special API for gift card redemption in BlockChyp.  Just execute a plain charge transaction and if the customer happens to swipe a gift card, our terminals will identify the gift card and run a gift card redemption.  Also note that if for some reason the gift card's original purchase transaction is associated with fraud or a chargeback, the transaction will be rejected.
-* **EBT**: Set the `ebt` flag to process an EBT SNAP transaction.  Note that test EBT transactions always assume a balance of $100.00, so test EBT transactions over that amount may be declined.
-* **Cash Back**: To enable cash back for debit transactions, set the `cashBack` flag.  If the card presented isn't a debit card, the `cashBack` flag will be ignored.
-* **Manual Card Entry**: Set the `manual` flag to enable manual card entry.  Good as a backup when chips and MSR's don't work or for more secure phone orders.  You can even combine the `manual` flag with the `ebt` flag for manual EBT card entry.
-* **Inline Tokenization**: You can enroll the payment method in the token vault inline with a charge transaction by setting the `enroll` flag.  You'll get a token back in the response.  You can even bind the token to a customer record if you also pass in customer data.
-* **Prompting for Tips**: Set the `promptForTips` flag if you'd like to prompt the customer for a tip before authorization.  Good for pay-at-the-table and other service related scenarios.
-* **Cash Discounting and Surcharging**:  The `surcharge` and `cashDiscount` flags can be used together to support cash discounting or surcharge problems. Consult the Cash Discount documentation for more details.
+* **Gift Card Redemption**:  There's no special API for gift card redemption in BlockChyp. Just execute a plain charge transaction and if the customer happens to swipe a gift card, our terminals will identify the gift card and run a gift card redemption. Also note that if for some reason the gift card's original purchase transaction is associated with fraud or a chargeback, the transaction will be rejected.
+* **EBT**: Set the `CardType` field to `CardType::EBT` to process an EBT SNAP transaction. Note that test EBT transactions always assume a balance of $100.00, so test EBT transactions over that amount may be declined.
+* **Cash Back**: To enable cash back for debit transactions, set the `CashBack` field. If the card presented isn't a debit card, the `CashBack` field will be ignored.
+* **Manual Card Entry**: Set the `ManualEntry` field to enable manual card entry. Good as a backup when chips and MSR's don't work or for more secure phone orders. You can even combine the `ManualEntry` field with the `CardType` field set to `CardType::EBT` for manual EBT card entry.
+* **Inline Tokenization**: You can enroll the payment method in the token vault inline with a charge transaction by setting the `Enroll` field. You'll get a token back in the response. You can even bind the token to a customer record if you also pass in customer data.
+* **Prompting for Tips**: Set the `PromptForTip` field if you'd like to prompt the customer for a tip before authorization. Good for pay-at-the-table and other service related scenarios.
+* **Cash Discounting and Surcharging**:  The `Surcharge` and `CashDiscount` fields can be used together to support cash discounting or surcharge problems. Consult the Cash Discount documentation for more details.
 
 
 
@@ -209,10 +209,10 @@ might be maliciously running on the point-of-sale system.
 
 **Common Variations**
 
-* **Manual Card Entry**: Set the `manual` flag to enable manual card entry.  Good as a backup when chips and MSR's don't work or for more secure phone orders.  You can even combine the `manual` flag with the `ebt` flag for manual EBT card entry.
-* **Inline Tokenization**: You can enroll the payment method in the token vault in line with a charge transaction by setting the `enroll` flag.  You'll get a token back in the response.  You can even bind the token to a customer record if you also pass in customer data.
-* **Prompting for Tips**: Set the `promptForTips` flag if you'd like to prompt the customer for a tip before authorization.  You can prompt for tips as part of a preauthorization, although it's not a very common approach.
-* **Cash Discounting and Surcharging**:  The `surcharge` and `cashDiscount` flags can be used together to support cash discounting or surcharge problems. Consult the Cash Discount documentation for more details.
+* **Manual Card Entry**: Set the `ManualEntry` field to enable manual card entry. Good as a backup when chips and MSR's don't work or for more secure phone orders. You can even combine the `ManualEntry` field with `CardType` set to `CardType::EBT` for manual EBT card entry.
+* **Inline Tokenization**: You can enroll the payment method in the token vault in line with a charge transaction by setting the `Enroll` field. You'll get a token back in the response. You can even bind the token to a customer record if you also pass in customer data.
+* **Prompting for Tips**: Set the `PromptForTip` field if you'd like to prompt the customer for a tip before authorization. You can prompt for tips as part of a preauthorization, although it's not a very common approach.
+* **Cash Discounting and Surcharging**: The `Surcharge` and `CashDiscount` fields can be used together to support cash discounting or surcharge problems. Consult the Cash Discount documentation for more details.
 
 
 
@@ -311,7 +311,7 @@ call this a *free range refund*.
 We don't recommend it, but it is permitted.  If you absolutely insist on
 doing it, pass in a Terminal Name and an amount.
 
-You can execute a manual or keyed refund by passing the `manual` flag
+You can execute a manual or keyed refund by passing the `ManualEntry` field
 to a free range refund request.
 
 **Gift Card Refunds**

data/lib/blockchyp/version.rb

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

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: blockchyp
 version: !ruby/object:Gem::Version
-  version: 2.8.1
+  version: 2.9.0
 platform: ruby
 authors:
 - BlockChyp
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2021-06-02 00:00:00.000000000 Z
+date: 2021-07-09 00:00:00.000000000 Z
 dependencies: []
 description: 
 email: