blockchyp 2.15.26 → 2.16.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 3deacf875401f15866ccb30d023d0fea003f9ae2a409097ff2467e4b83626858
-  data.tar.gz: cda2f4369908eeaba76d25c98b1bdb8e8ccc7b1f843c5af984cae13c840f728b
+  metadata.gz: 9ceadb4c33463ac72dfd6c087bb1cc16f8e5ef584b39037ee636e1fad8151855
+  data.tar.gz: c4f2f23bc8385debcee9967904c80150192ef4d58fbd4c303541bdf6af90cd7e
 SHA512:
-  metadata.gz: 91d9ab49675b04289c980d7da4eb5c1dbfe5f6454a8f212c74f4caca781134307453a17699c4a45fac2d8ca946838094d7477f5744c87983e8750673ded26189
-  data.tar.gz: 2b5f2b95df428d1bf31a105d99961a262a7d27c5288126212bea1e7bb2de80fab5cef175ad70fdedaf965580d4775dec9a54ad781b5a3a3f98dc0bf7094e1c1f
+  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.15.26'
+  VERSION = '2.16.2'
 end

metadata

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