blockchyp 2.16.0 → 2.16.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: fe7037d65ec09a0063f12853668503f52cb0e6fbaedaf14897891b119bc5d162
-  data.tar.gz: f5b7ad3c162d1743e3d1767aa6545df60aabd9cc03f38ea474137518fcf77bf3
+  metadata.gz: 9ceadb4c33463ac72dfd6c087bb1cc16f8e5ef584b39037ee636e1fad8151855
+  data.tar.gz: c4f2f23bc8385debcee9967904c80150192ef4d58fbd4c303541bdf6af90cd7e
 SHA512:
-  metadata.gz: 3a0acaa000891e335405cc60b86520c4e1955fbf6cbdb423c25e5a1bb2c2aadd89472fe6830c91c0781dbaf03feca36eddc23273f030275286c707514ab7520b
-  data.tar.gz: 590de5bb268b093fd1e843ffa901f93f969ee22da3957f763e3cd34af437ca2be736647bfa262b6668089ee1393965851338b7ae85f6d3207f097d718e8c5d0e
+  metadata.gz: 4a164e7dd56813fe7ea43a560400f3add70cd1f65fe2f3ebc8f1ff9fd39241093f8d7024c4c7bb3c4f2436d6b0c7e99ce16ea51f0807a98ef857f48a0c29b00e
+  data.tar.gz: 8af811cd6c4ac3270c5092880ebe4ec46235af7d81422c36ba7479d3fb222b2449dceaa87f1f2d8130d6adf7baa048de4d03f19f002cc9c2eaede18ec1965469

data/README.md

@@ -737,10 +737,10 @@ same format as all BlockChyp charge and preauth transaction responses.
 **Status Polling**
 
 If real time callbacks aren't practical or necessary in your environment, you can
-always use the Transaction Status API described below.
+always use the Payment Link Status API described futher on.
 
 A common use case for the send link API with status polling is curbside pickup.
-You could have your system check the Transaction Status when a customer arrives to
+You could have your system check the Payment Link Status when a customer arrives to
 ensure it's been paid without necessarily needing to create background threads
 to constantly poll for status updates.
 
@@ -875,6 +875,15 @@ puts "Response: #{response.inspect}"
 This API allows you to check on the status of a payment link, including transaction data
 and the full history of attempted transactions.
 
+This API is the preferred source of truth and best practice when you want to check on the 
+status of a payment link (as opposed to Transaction Status). The Transaction Status API is not 
+ideal because of ambiguity when there are multiple transactions associated with a single 
+payment link.
+
+You must pass the `linkCode` value associated with the payment link. It is included in the response from BlockChyp when the payment link is originally created.
+
+
+
 
 
 
@@ -911,7 +920,7 @@ puts "Response: #{response.inspect}"
 This API returns the current status for any transaction.  You can lookup a transaction
 by its BlockChyp assigned Transaction ID or your own Transaction Ref.
 
-You should alway use globally unique Transaction Ref values, but in the event
+You should always use globally unique Transaction Ref values, but in the event
 that you duplicate Transaction Refs, the most recent transaction matching your
 Transaction Ref is returned.
 

data/lib/blockchyp/version.rb

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

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: blockchyp
 version: !ruby/object:Gem::Version
-  version: 2.16.0
+  version: 2.16.2
 platform: ruby
 authors:
 - BlockChyp
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2023-08-18 00:00:00.000000000 Z
+date: 2023-08-24 00:00:00.000000000 Z
 dependencies: []
 description: 
 email: