blockchyp 2.16.0 → 2.16.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: fe7037d65ec09a0063f12853668503f52cb0e6fbaedaf14897891b119bc5d162
-  data.tar.gz: f5b7ad3c162d1743e3d1767aa6545df60aabd9cc03f38ea474137518fcf77bf3
+  metadata.gz: 49fe4c55af2de1c7aa6e0236d4416b7d83f1283e478cea60250713604aff3e0a
+  data.tar.gz: 285d113837e076bac757f33fdce0ae7fa5793ee3217dd93a0a3590c2e4b6160f
 SHA512:
-  metadata.gz: 3a0acaa000891e335405cc60b86520c4e1955fbf6cbdb423c25e5a1bb2c2aadd89472fe6830c91c0781dbaf03feca36eddc23273f030275286c707514ab7520b
-  data.tar.gz: 590de5bb268b093fd1e843ffa901f93f969ee22da3957f763e3cd34af437ca2be736647bfa262b6668089ee1393965851338b7ae85f6d3207f097d718e8c5d0e
+  metadata.gz: dfcb5489b6d1a11e6fa5163f357eaeb1fdf2cab25287e8a11f4c583c05660f1f775db71e432a41c819de0987626be913c07d3afee112f46c603dc152ac471029
+  data.tar.gz: 134f3fc9624de085885d07972165dd78202d1873fde8559dcc1a2fd985513ccf688757d6186e595e9d32d3c898454db26d79a5ce4041d035e2ffb94ec2a287ab

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.
+
+
+
 
 
 
@@ -891,7 +900,7 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
-  linkCode: response[:linkCode]
+  linkCode: '<PAYMENT LINK CODE>'
 }
 
 response = blockchyp.paymentLinkStatus(request)
@@ -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.4'
 end

data/test/payment_link_status_test.rb

@@ -60,7 +60,7 @@ module BlockChyp
 
       # Set request parameters
       request = {
-        transactionRef: response[:transactionRef]
+        linkCode: response[:linkCode]
       }
 
       response = blockchyp.payment_link_status(request)

data/test/resend_payment_link_test.rb

@@ -31,9 +31,32 @@ module BlockChyp
 
       # Set request parameters
       setup_request = {
-        linkCode: response[:linkCode]
+        amount: '199.99',
+        description: 'Widget',
+        subject: 'Widget invoice',
+        transaction: {
+          subtotal: '195.00',
+          tax: '4.99',
+          total: '199.99',
+          items: [
+            {
+              description: 'Widget',
+              price: '195.00',
+              quantity: 1
+            }
+          ]
+        },
+        autoSend: true,
+        customer: {
+          customerRef: 'Customer reference string',
+          firstName: 'FirstName',
+          lastName: 'LastName',
+          companyName: 'Company Name',
+          emailAddress: 'notifications@blockchypteam.m8r.co',
+          smsNumber: '(123) 123-1231'
+        }
       }
-      response = blockchyp.resend_payment_link(setup_request)
+      response = blockchyp.send_payment_link(setup_request)
 
       # Set request parameters
       request = {

metadata

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