blockchyp 2.12.1 → 2.13.0

data/README.md

@@ -74,84 +74,19 @@ You can also view a number of long form demos and learn more about us on our [Yo
 You don't want to read words. You want examples. Here's a quick rundown of the
 stuff you can do with the BlockChyp Ruby SDK and a few basic examples.
 
-#### Terminal Ping
-
-
-This simple test transaction helps ensure you have good communication with a payment terminal and is usually the first one you'll run in development.
-
-It tests communication with the terminal and returns a positive response if everything
-is okay.  It works the same way in local or cloud relay mode.
-
-If you get a positive response, you've successfully verified all of the following:
-
-* The terminal is online.
-* There is a valid route to the terminal.
-* The API Credentials are valid.
-
-
-
-
-```ruby
-# frozen_string_literal: true
-
-require 'blockchyp'
-
-blockchyp = BlockChyp::BlockChyp.new(
-  ENV['BC_API_KEY'],
-  ENV['BC_BEARER_TOKEN'],
-  ENV['BC_SIGNING_KEY']
-)
-
-# Set request parameters
-request = {
-  terminalName: 'Test Terminal'
-}
-
-response = blockchyp.ping(request)
-
-puts "Response: #{response.inspect}"
-
-
-```
-
-#### Terminal Locate
-
-
-This endpoint returns routing and location information for a terminal.
-
-The result will indicate whether or not the terminal is in cloud relay mode and will
-return the local IP address if the terminal is in local mode.
-
-The terminal will also return the public key for the terminal.
-
+### Payment Endpoints
 
 
+These are the core payment APIs used to execute and work with payment transactions in BlockChyp.
 
-```ruby
-# frozen_string_literal: true
-
-require 'blockchyp'
-
-blockchyp = BlockChyp::BlockChyp.new(
-  ENV['BC_API_KEY'],
-  ENV['BC_BEARER_TOKEN'],
-  ENV['BC_SIGNING_KEY']
-)
-
-# Set request parameters
-request = {
-  terminalName: 'Test Terminal'
-}
-
-response = blockchyp.locate(request)
 
-puts "Response: #{response.inspect}"
 
+#### Charge
 
-```
 
-#### Charge
 
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
 
 Our most popular transaction executes a standard authorization and capture.
 This is the most basic of
@@ -171,21 +106,21 @@ property instead.
 
 **Card Numbers and Mag Stripes**
 
-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
+You can also pass in PANs and Mag Stripes, but you probably shouldn't, as this will
+put you in PCI scope and the most common vector for POS breaches is keylogging.
+If you use terminals for manual card entry, you'll bypass any keyloggers 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.
+* **Gift Card Redemption**:  There's no special API for gift card redemption in BlockChyp. Simply execute a plain charge transaction and if the customer swipes 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.
-
+* **Cryptocurrency** The `Cryptocurrency` field can be used to switch the standard present card screen to a cryptocurrency screen.  The field value can be `ANY` to enable any supported cryptocurrency or a single currency code such as `BTC` for Bitcoin.
 
 
 
@@ -217,9 +152,13 @@ puts "Response: #{response.inspect}"
 #### Preauthorization
 
 
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
 A preauthorization puts a hold on funds and must be captured later.  This is used
-in scenarios where the final transaction amount might change.  A common examples would
-be fine dining where a tip adjustment is required prior to final settlement.
+in scenarios where the final transaction amount might change.  A common example is 
+fine dining, where a tip adjustment is required before final settlement.
 
 Another use case for preauthorization is e-commerce.  Typically, an online order
 is preauthorized at the time of the order and then captured when the order ships.
@@ -238,11 +177,15 @@ 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, as 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.
 
+**Cryptocurrency**
+
+Note that preauths are not supported for cryptocurrency.
+
 **Common Variations**
 
 * **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.
@@ -281,14 +224,19 @@ puts "Response: #{response.inspect}"
 #### Capture Preauthorization
 
 
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
 This API allows you to capture a previously approved preauthorization.
 
-You'll need to make sure you pass in the Transaction ID returned by the original preauth transaction so we know which transaction we're capturing.  If you want to capture the transaction for the
+You'll need to make sure you pass in the Transaction ID returned by the original preauth transaction 
+so we know which transaction we're capturing.  If you want to capture the transaction for the
 exact amount of the preauth, the Transaction ID is all you need to pass in.
 
 You can adjust the total if you need to by passing in a new `amount`.  We
 also recommend you pass in updated amounts for `tax` and `tip` as it can
-reduce your interchange fees in some cases. (Level II Processing, for example.)
+sometimes reduce your interchange fees. (Level II Processing, for example.)
 
 
 
@@ -307,7 +255,8 @@ blockchyp = BlockChyp::BlockChyp.new(
 # Set request parameters
 request = {
   test: true,
-  transactionId: '<PREAUTH TRANSACTION ID>'
+  transactionId: '<ORIGINAL TRANSACTION ID>',
+  amount: '32.00'
 }
 
 response = blockchyp.capture(request)
@@ -320,6 +269,10 @@ puts "Response: #{response.inspect}"
 #### Refund
 
 
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
 It's not ideal, but sometimes customers want their money back.
 
 Our refund API allows you to confront this unpleasant reality by executing refunds in a few different scenarios.
@@ -330,21 +283,21 @@ returned in a BlockChyp response.  To refund the full amount of the previous tra
 **Partial Refunds**
 
 For a partial refund, just pass in an amount along with the Transaction ID.
-The only rule is that the amount has to be equal to or less than the original
+The only rule is that the amount must be equal to or less than the original
 transaction.  You can execute multiple partial refunds against the same
 original transaction as long as the total refunded amount doesn't exceed the original amount.
 
 **Tokenized Refunds**
 
 You can also use a token to execute a refund.  Pass in a token instead
-of the Transaction ID along with the desired refund amount.
+of the Transaction ID and the desired refund amount.
 
 **Free Range Refunds**
 
 When you execute a refund without referencing a previous transaction, we
 call this a *free range refund*.
 
-We don't recommend it, but it is permitted.  If you absolutely insist on
+We don't recommend this type of refund, 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 `ManualEntry` field
@@ -366,6 +319,11 @@ If a refund referencing a previous transaction is executed for the full amount
 before the original transaction's batch is closed, the refund is automatically
 converted to a void.  This saves the merchant a little bit of money.
 
+**Cryptocurrency**
+
+Note that refunds are not supported for cryptocurrency.  You must refund crypto transactions
+manually from your cryptocurrency wallet.
+
 
 
 
@@ -393,64 +351,26 @@ response = blockchyp.refund(request)
 puts "Response: #{response.inspect}"
 
 
-```
-
-#### Enroll
-
-
-This API allows you to tokenize and enroll a payment method in the token
-vault.  You can also pass in customer information and associate the
-payment method with a customer record.
-
-A token is returned in the response that can be used in subsequent charge,
-preauth, and refund transactions.
-
-**Gift Cards and EBT**
-
-Gift Cards and EBT cards cannot be tokenized.
-
-**E-Commerce Tokens**
-
-The tokens returned by the enroll API and the e-commerce web tokenizer
-are the same tokens and can be used interchangeably.
-
-
-
-
-```ruby
-# frozen_string_literal: true
-
-require 'blockchyp'
-
-blockchyp = BlockChyp::BlockChyp.new(
-  ENV['BC_API_KEY'],
-  ENV['BC_BEARER_TOKEN'],
-  ENV['BC_SIGNING_KEY']
-)
-
-# Set request parameters
-request = {
-  test: true,
-  terminalName: 'Test Terminal'
-}
-
-response = blockchyp.enroll(request)
-
-puts "Response: #{response.inspect}"
-
-
 ```
 
 #### Void
 
 
 
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
 Mistakes happen.  If a transaction is made by mistake, you can void it
 with this API.  All that's needed is to pass in a Transaction ID and execute
 the void before the original transaction's batch closes.
 
 Voids work with EBT and gift card transactions with no additional parameters.
 
+**Cryptocurrency**
+
+Note that voids are not supported for cryptocurrency.  You must refund crypto transactions
+manually from your cryptocurrency wallet.
+
 
 
 
@@ -482,6 +402,9 @@ puts "Response: #{response.inspect}"
 
 
 
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
 Payment transactions require a stable network to function correctly and
 no network is stable all the time.  Time out reversals are a great line
 of defense against accidentally double charging consumers when payments
@@ -496,9 +419,14 @@ The only caveat is that developers must use the `transactionRef` property (`txRe
 
 The reason for this requirement is that if a system never receives a definitive
 response for a transaction, the system would never have received the BlockChyp
-generated Transaction ID.  We have to fallback to Transaction Ref to identify
+generated Transaction ID.  We have to fall back to Transaction Ref to identify
 a transaction.
 
+**Cryptocurrency**
+
+Note that refunds are not supported for cryptocurrency.  You must refund crypto transactions
+manually from your cryptocurrency wallet.
+
 
 
 
@@ -528,14 +456,18 @@ puts "Response: #{response.inspect}"
 #### Gift Card Activation
 
 
-This API can be used to activate or add value to BlockChyp gift cards.
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+This API activates or adds value to BlockChyp gift cards.
 Just pass in the terminal name and the amount to add to the card.
 Once the customer swipes their card, the terminal will use keys
 on the mag stripe to add value to the card.
 
 You don't need to handle a new gift card activation or a gift card recharge any
 differently.  The terminal firmware will figure out what to do on its
-own and also returns the new balance for the gift card.
+own while also returning the new balance for the gift card.
 
 This is the part of the system where BlockChyp's blockchain DNA comes
 closest to the surface.  The BlockChyp gift card system doesn't really
@@ -564,9 +496,9 @@ voiding or reversing a conventional payment transaction.
 
 BlockChyp does have the ability to import gift card liability from
 conventional gift card platforms.  Unfortunately, BlockChyp does not
-support activating cards on third party systems, but you can import
+support activating cards on third party systems.  However, you can import
 your outstanding gift cards and customers can swipe them on the
-terminals just like BlockChyp's standard gift cards.
+terminals like BlockChyp's standard gift cards.
 
 No special coding is required to access this feature.  The gateway and
 terminal firmware handle everything for you.
@@ -576,7 +508,7 @@ terminal firmware handle everything for you.
 BlockChyp does not currently provide any native support for other gift card
 platforms beyond importing gift card liability.  We do have a white listing system
 that can be used to support your own custom gift card implementations.  We have a security review
-process before we allow a BIN range to be white listed, so contact
+process before we can allow a BIN range to be white listed, so contact
 support@blockchyp.com if you need to white list a BIN range.
 
 
@@ -611,25 +543,29 @@ puts "Response: #{response.inspect}"
 
 
 
-Checks a gift or EBT card balance.
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+This API checks a gift or EBT card balance.
 
 **Gift Card Balance Checks**
 
-For gift cards, just pass in a terminal name and the customer will be prompted
+For gift cards, pass in a terminal name and the customer will be prompted
 to swipe a card on that terminal.  The remaining balance will be displayed
 briefly on the terminal screen and the API response will include the gift card's public key and the remaining balance.
 
 **EBT Balance Checks**
 
-All EBT transactions require a PIN, so in order to check an EBT card balance,
+All EBT transactions require a PIN, so to check an EBT card balance,
 you need to pass in the `ebt` flag just like you would for a normal EBT
 charge transaction.  The customer will be prompted to swipe their card and
-enter a PIN code.  If everything checks out, the remaining balance on the card will be displayed on the terminal for the customer and returned in the API.
+enter a PIN code.  If everything checks out, the remaining balance on the 
+card will be displayed on the terminal for the customer and returned with the API response.
 
 **Testing Gift Card Balance Checks**
 
 Test gift card balance checks work no differently than live gift cards.  You
-must activate a test gift card first in order to test balance checks.  Test
+must activate a test gift card first to test balance checks.  Test
 gift cards are real blockchain cards that live on our parallel test blockchain.
 
 **Testing EBT Gift Card Balance Checks**
@@ -668,6 +604,10 @@ puts "Response: #{response.inspect}"
 #### Close Batch
 
 
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
 This API will close the merchant's batch if it's currently open.
 
 By default, merchant batches will close automatically at 3 AM in their
@@ -706,6 +646,9 @@ puts "Response: #{response.inspect}"
 
 
 
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
 This API allows you to send an invoice to a customer and capture payment
 via a BlockChyp hosted payment page.
 
@@ -720,26 +663,26 @@ you use the `cashier` flag.)
 
 **Customer Info**
 
-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.
+Unless you're using the `cashier` flag, you must specify a customer; either by
+creating a new customer record inline or 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
-detail with every request.  It will make the invoice look a little more complete
+detail with every request.  It will make the invoice look 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 provide a free form description or message that's displayed near
+You can also provide a free form description or message to display near
 the bottom of the invoice.  Usually this is some kind of thank you note
 or instruction.
 
 **Terms and Conditions**
 
 You can include long form contract language with a request and capture
-terms and conditions acceptance at the same time payment is captured.
+terms and conditions accepted at the same time payment is captured.
 
 The interface is identical to that used for the terminal based Terms and
 Conditions API in that you can pass in content directly via `tcContent` or via
@@ -748,10 +691,14 @@ agreement acceptance is incorporated into a send link request.
 
 **Auto Send**
 
-BlockChyp does not send the email notification automatically.  This is
-a safeguard to prevent real emails from going out when you may not expect it.
-If you want BlockChyp to send the email for you, just add the `autoSend` flag with
-all requests.
+BlockChyp does not send the email notification automatically.   This safeguard prevents real 
+emails from going out when you may not expect them If you want BlockChyp to send the email 
+for you, just add the `autoSend` flag with all requests.
+
+**Cryptocurrency**
+
+If the merchant is configured to support cryptocurrency transactions, the payment page will
+display additional UI widgets that allowing customers to switch to a crypto payment method.
 
 **Tokenization**
 
@@ -761,13 +708,15 @@ in the token vault.
 **Cashier Facing Card Entry**
 
 BlockChyp can be used to generate internal/cashier facing card entry pages as well.  This is
-designed for situations where you might need to take a phone order and you don't
-have a terminal.
+designed for situations where you might need to take a phone order and don't
+have an available terminal.
 
-If you pass in the `cashier` flag, no email will be sent and you'll be be able to
+If you pass in the `cashier` flag, no email will be sent and you'll 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.
 
+Note that cryptocurrency is not supported for cashier facing payment entry.
+
 **Payment Notifications**
 
 When a customer successfully submits payment, the merchant will receive an email
@@ -809,6 +758,7 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
+  transactionRef: '<TX REF>',
   amount: '199.99',
   description: 'Widget',
   subject: 'Widget invoice',
@@ -846,7 +796,10 @@ puts "Response: #{response.inspect}"
 
 
 
-Cancels a payment link.
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+This API cancels a payment link.
 
 
 
@@ -864,7 +817,7 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
-  linkCode: 'Payment link code to cancel'
+  linkCode: '<PAYMENT LINK CODE>'
 }
 
 response = blockchyp.cancelPaymentLink(request)
@@ -878,7 +831,10 @@ puts "Response: #{response.inspect}"
 
 
 
-Returns the current status for any transaction.  You can lookup a transaction
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+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
@@ -901,7 +857,7 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
-  transactionId: 'ID of transaction to retrieve'
+  transactionId: '<TRANSACTION ID>'
 }
 
 response = blockchyp.transactionStatus(request)
@@ -911,13 +867,18 @@ puts "Response: #{response.inspect}"
 
 ```
 
-#### Terminal Clear
+#### Cash Discount
 
 
 
-This API interrupts whatever a terminal may be doing and returns it to the
-idle state.
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+This API calculates the surcharge, cash discount, and total amounts for cash transactions.
 
+If you're using BlockChyp's cash discounting features, you can use this endpoint
+to ensure the numbers and receipts for true cash transactions are consistent
+with transactions processed by BlockChyp.
 
 
 
@@ -935,31 +896,46 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
-  test: true,
-  terminalName: 'Test Terminal'
+  amount: '100.00',
+  cashDiscount: true,
+  surcharge: true
 }
 
-response = blockchyp.clear(request)
+response = blockchyp.cashDiscount(request)
 
 puts "Response: #{response.inspect}"
 
 
 ```
 
-#### Terminal Status
+#### Batch History
 
 
 
-Returns the current status of a payment terminal.  This is typically used
-as a way to determine if the terminal is busy before sending a new transaction.
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
 
-If the terminal is busy, `idle` will be false and the `status` field will return
-a short string indicating the transaction type currently in progress.  The system
-will also return the timestamp of the last status change in the `since` field.
+This endpoint allows developers to query the gateway for the merchant's batch history.
+The data will be returned in descending order of open date with the most recent
+batch returned first.  The results will include basic information about the batch.
+Consider using the Batch Details API for more detail about a specific batch.
 
-If the system is running a payment transaction and you wisely passed in a
-Transaction Ref, this API will also return the Transaction Ref of the in progress
-transaction.
+**Limiting Results**
+
+This API will return a maximum of 250 results.  Use the `maxResults` property to
+limit maximum results even further and use the `startIndex` property to
+page through results that span multiple queries.
+
+For example, if you want the ten most recent batches, pass in a value of
+`10` for `maxResults`.  Also note that `startIndex` is zero based. Use a value of `0` to
+get the first batch in the dataset.
+
+**Filtering by Date Range**
+
+You can also filter results by date.  Use the `startDate` and `endDate`
+properties to return only those batches opened between those dates.
+You can use either `startDate` and `endDate` and you can use date filters
+in conjunction with `maxResults` and `startIndex`
 
 
 
@@ -977,57 +953,31 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
-  terminalName: 'Test Terminal'
+  maxResults: 250,
+  startIndex: 0
 }
 
-response = blockchyp.terminalStatus(request)
+response = blockchyp.batchHistory(request)
 
 puts "Response: #{response.inspect}"
 
 
 ```
 
-#### Terms & Conditions Capture
-
-
-
-This API allows you to prompt a customer to accept a legal agreement on the terminal
-and (usually) capture their signature.
-
-Content for the agreement can be specified in two ways.  You can reference a
-previously configured T&C template or pass in the full agreement text with every request.
-
-**Using Templates**
-
-If your application doesn't keep track of agreements you can leverage BlockChyp's
-template system.  You can create any number of T&C Templates in the merchant dashboard
-and pass in the `tcAlias` flag to specify which one to display.
-
-**Raw Content**
-
-If your system keeps track of the agreement language or executes complicated merging
-and rendering logic, you can bypass our template system and pass in the full text with
-every transaction.  Use the `tcName` to pass in the agreement name and `tcContent` to
-pass in the contract text.  Note that only plain text is supported.
-
-**Bypassing Signatures**
-
-Signature images are captured by default.  If for some reason this doesn't fit your
-use case and you'd like to capture acceptance without actually capturing a signature image, set
-the `disableSignature` flag in the request.
+#### Batch Details
 
-**Terms & Conditions Log**
 
-Every time a user accepts an agreement on the terminal, the signature image (if captured),
-will be uploaded to the gateway and added to the log along with the full text of the
-agreement.  This preserves the historical record in the event that standard agreements
-or templates change over time.
 
-**Associating Agreements with Transactions**
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
 
-To associate a Terms & Conditions log entry with a transaction, just pass in the
-Transaction ID or Transaction Ref for the associated transaction.
+This API allows developers to pull down details for a specific batch,
+including captured volume, gift card activity, expected deposit, and
+captured volume broken down by terminal.
 
+The only required request parameter is `batchId`.  Batch IDs are returned
+with every transaction response and can be discovered using the Batch
+History API.
 
 
 
@@ -1045,58 +995,68 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
-  test: true,
-  terminalName: 'Test Terminal',
-
-  # Alias for a Terms and Conditions template configured in the BlockChyp
-  # dashboard.
-  tcAlias: 'hippa',
-
-  # Name of the contract or document if not using an alias.
-  tcName: 'HIPPA Disclosure',
-
-  # Full text of the contract or disclosure if not using an alias.
-  tcContent: 'Full contract text',
-
-  # File format for the signature image.
-  sigFormat: SignatureFormat::PNG,
-
-  # Width of the signature image in pixels.
-  sigWidth: 200,
-
-  # Whether or not a signature is required. Defaults to true.
-  sigRequired: true
+  batchId: '<BATCH ID>'
 }
 
-response = blockchyp.termsAndConditions(request)
+response = blockchyp.batchDetails(request)
 
 puts "Response: #{response.inspect}"
 
 
 ```
 
-#### Capture Signature
+#### Transaction History
 
 
 
-This endpoint captures a written signature from the terminal and returns the
-image.
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
 
-Unlike the Terms & Conditions API, this endpoint performs basic signature
-capture with no agreement display or signature archival.
+This endpoint provides several different methods to sift through
+transaction history.
 
-Under the hood, signatures are captured in a proprietary vector format and
-must be converted to a common raster format in order to be useful to most
-applications.  At a minimum, you must specify an image format using the
-`sigFormat` parameter.  As of this writing JPG and PNG are supported.
+By default with no filtering properties, this endpoint will return the 250
+most recent transactions.
 
-By default, images are returned in the JSON response as hex encoded binary.
-You can redirect the binary image output to a file using the `sigFile`
-parameter.
+**Limiting Results**
 
-You can also scale the output image to your preferred width by
-passing in a `sigWidth` parameter.  The image will be scaled to that
-width, preserving the aspect ratio of the original image.
+This API will return a maximum of 50 results in a single query.  Use the `maxResults` property
+to limit maximum results even further and use the `startIndex` property to
+page through results that span multiple queries.
+
+For example, if you want the ten most recent batches, pass in a value of
+`10` for `maxResults`.  Also note that `startIndex` is zero based. Use a value of `0` to
+get the first transaction in the dataset.
+
+**Filtering By Date Range**
+
+You can also filter results by date.  Use the `startDate` and `endDate`
+properties to return only transactions run between those dates.
+You can use either `startDate` or `endDate` and you can use date filters
+in conjunction with `maxResults` and `startIndex`
+
+**Filtering By Batch**
+
+To restrict results to a single batch, pass in the `batchId` parameter.
+
+**Filtering By Terminal**
+
+To restrict results to those executed on a single terminal, pass in the terminal name.
+
+**Combining Filters**
+
+None of the above filters are mutually exclusive.  You can combine any of the
+above properties in a single request to restrict transaction results to a
+narrower set of results.
+
+**Searching Transaction History**
+
+You can search transaction history by passing in search criteria with the 
+`query` option.  The search system will match the amount (requested and authorized),
+last four of the card number, cardholder name, and the auth code.
+
+Note that when search queries are used, terminalName or 
+batch id filters are not supported.
 
 
 
@@ -1114,45 +1074,119 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
-  terminalName: 'Test Terminal',
+  maxResults: 10,
+  batchId: '<BATCH ID>'
+}
 
-  # File format for the signature image.
-  sigFormat: SignatureFormat::PNG,
+response = blockchyp.transactionHistory(request)
 
-  # Width of the signature image in pixels.
-  sigWidth: 200
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### List Queued Transactions
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+Returns a list of transaction refs of transactions queued on a terminal.
+Details about the transactions can be retrieved using the Transaction Status
+API.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  terminalName: 'Test Terminal'
 }
 
-response = blockchyp.captureSignature(request)
+response = blockchyp.listQueuedTransactions(request)
 
 puts "Response: #{response.inspect}"
 
 
 ```
 
-#### New Transaction Display
+#### Delete Queued Transaction
 
 
 
-Sends totals and line item level data to the terminal.
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
 
-At a minimum, you should send total information as part of a display request,
-including `total`, `tax`, and `subtotal`.
+Deletes one or all queued transactions from a terminal. If `*` is passed as
+a transaction ref, then the entire terminal queue will be cleared. An error is
+returned if the passed transaction ref is not queued on the terminal.
 
-You can also send line item level data and each line item can have a `description`,
-`qty`, `price`, and `extended` price.
 
-If you fail to send an extended price, BlockChyp will multiply the `qty` by the
-`price`, but we strongly recommend you precalculate all the fields yourself
-to ensure consistency.  Your treatment of floating-point multiplication and rounding
-may differ slightly from BlockChyp's, for example.
 
-**Discounts**
 
-You have the option to show discounts on the display as individual line items
-with negative values or you can associate discounts with a specific line item.
-You can apply any number of discounts to an individual line item with a description
-and amount.
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  terminalName: 'Test Terminal',
+  transactionRef: '*'
+}
+
+response = blockchyp.deleteQueuedTransaction(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+### Terminal Management Endpoints
+
+
+These APIs support terminal management functions and additional terminal 
+features such as line item display, messages, and interactive prompts.  
+These features can be used to extend a point of sale system's functionality.
+
+
+
+#### Terminal Ping
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+This simple test transaction helps ensure good communication with a payment terminal 
+and is usually the first test you'll run in development.
+
+It tests communication with the terminal and returns a positive response if everything
+is okay.  It works the same way in local or cloud relay mode.
+
+If you get a positive response, you've successfully verified all of the following:
+
+* The terminal is online.
+* There is a valid route to the terminal.
+* The API Credentials are valid.
 
 
 
@@ -1170,67 +1204,66 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
-  test: true,
-  terminalName: 'Test Terminal',
-  transaction: {
-    subtotal: '60.00',
-    tax: '5.00',
-    total: '65.00',
-    items: [
-      {
-        description: 'Leki Trekking Poles',
-        price: '35.00',
-        quantity: 2,
-        extended: '70.00',
-        discounts: [
-          {
-            description: 'memberDiscount',
-            amount: '10.00'
-          }
-        ]
-      }
-    ]
-  }
+  terminalName: 'Test Terminal'
 }
 
-response = blockchyp.newTransactionDisplay(request)
+response = blockchyp.ping(request)
 
 puts "Response: #{response.inspect}"
 
 
 ```
 
-#### Update Transaction Display
+#### Terminal Locate
 
 
 
-Similar to *New Transaction Display*, this variant allows developers to update
-line item level data currently being displayed on the terminal.
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
 
-This is designed for situations where you want to update the terminal display as
-items are scanned.  This variant means you only have to send information to the
-terminal that's changed, which usually means the new line item and updated totals.
+This endpoint returns a terminal's routing and location information.
 
-If the terminal is not in line item display mode and you invoke this endpoint,
-the first invocation will behave like a *New Transaction Display* call.
+The result will indicate whether or not the terminal is in cloud relay mode and will
+return the local IP address if the terminal is in local mode.
 
-At a minimum, you should send total information as part of a display request,
-including `total`, `tax`, and `subtotal`.
+The terminal will also return the public key for the terminal.
 
-You can also send line item level data and each line item can have a `description`,
-`qty`, `price`, and `extended` price.
 
-If you fail to send an extended price, BlockChyp will multiply the `qty` by the
-`price`, but we strongly recommend you precalculate all the fields yourself
-to ensure consistency.  Your treatment of floating-point multiplication and rounding
-may differ slightly from BlockChyp's, for example.
 
-**Discounts**
 
-You have the option to show discounts on the display as individual line items
-with negative values or you can associate discounts with a specific line item.
-You can apply any number of discounts to an individual line item with a description
-and amount.
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  terminalName: 'Test Terminal'
+}
+
+response = blockchyp.locate(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Terminal Clear
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+This API interrupts whatever a terminal may be doing and returns it to the
+idle state.
+
 
 
 
@@ -1249,42 +1282,1594 @@ blockchyp = BlockChyp::BlockChyp.new(
 # Set request parameters
 request = {
   test: true,
-  terminalName: 'Test Terminal',
-  transaction: {
-    subtotal: '60.00',
-    tax: '5.00',
-    total: '65.00',
-    items: [
-      {
-        description: 'Leki Trekking Poles',
-        price: '35.00',
-        quantity: 2,
-        extended: '70.00',
-        discounts: [
-          {
-            description: 'memberDiscount',
-            amount: '10.00'
-          }
-        ]
-      }
-    ]
-  }
+  terminalName: 'Test Terminal'
 }
 
-response = blockchyp.updateTransactionDisplay(request)
+response = blockchyp.clear(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Terminal Status
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+This API returns the current status of a payment terminal.  This is typically used
+as a way to determine if the terminal is busy before sending a new transaction.
+
+If the terminal is busy, `idle` will be false and the `status` field will return
+a short string that indicates the transaction type currently in progress.  The system
+will also return the timestamp of the last status change in the `since` field.
+
+If the system is running a payment transaction and you wisely passed in a
+Transaction Ref, this API will also return the Transaction Ref of the in progress
+transaction.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  terminalName: 'Test Terminal'
+}
+
+response = blockchyp.terminalStatus(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Capture Signature
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+This endpoint captures a written signature from the terminal and returns the
+image.
+
+Unlike the Terms & Conditions API, this endpoint performs basic signature
+capture with no agreement display or signature archival.
+
+Under the hood, signatures are captured in a proprietary vector format and
+must be converted to a common raster format in order to be useful to most
+applications.  At a minimum, you must specify an image format using the
+`sigFormat` parameter.  Currently, JPG and PNG are supported.
+
+By default, images are returned in the JSON response as hex encoded binary.
+You can redirect the binary image output to a file using the `sigFile`
+parameter.
+
+You can also scale the output image to your preferred width by
+passing in a `sigWidth` parameter.  The image will be scaled to that
+width, preserving the aspect ratio of the original image.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  terminalName: 'Test Terminal',
+
+  # File format for the signature image.
+  sigFormat: SignatureFormat::PNG,
+
+  # Width of the signature image in pixels.
+  sigWidth: 200
+}
+
+response = blockchyp.captureSignature(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### New Transaction Display
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+This API sends totals and line item level data to the terminal.
+
+At a minimum, you should send total information as part of a display request,
+including `total`, `tax`, and `subtotal`.
+
+You can also send line item level data and each line item can have a `description`,
+`qty`, `price`, and `extended` price.
+
+If you fail to send an extended price, BlockChyp will multiply the `qty` by the
+`price`.  However, we strongly recommend you precalculate all the fields yourself
+to ensure consistency.  For example, your treatment of floating-point multiplication 
+and rounding may differ slightly from BlockChyp's.
+
+**Discounts**
+
+You have the option to show discounts on the display as individual line items
+with negative values or you can associate discounts with a specific line item.
+You can apply any number of discounts to an individual line item with a description
+and amount.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  test: true,
+  terminalName: 'Test Terminal',
+  transaction: {
+    subtotal: '60.00',
+    tax: '5.00',
+    total: '65.00',
+    items: [
+      {
+        description: 'Leki Trekking Poles',
+        price: '35.00',
+        quantity: 2,
+        extended: '70.00',
+        discounts: [
+          {
+            description: 'memberDiscount',
+            amount: '10.00'
+          }
+        ]
+      }
+    ]
+  }
+}
+
+response = blockchyp.newTransactionDisplay(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Update Transaction Display
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+Similar to *New Transaction Display*, this variant allows developers to update
+line item level data currently being displayed on the terminal.
+
+This feature is designed for situations where you want to update the terminal display as
+items are scanned.  You'll only have to send information to the
+terminal that's changed, which usually means the new line item and updated totals.
+
+If the terminal is not in line item display mode and you invoke this endpoint,
+the first invocation will behave like a *New Transaction Display* call.
+
+At a minimum, you should send total information as part of a display request,
+including `total`, `tax`, and `subtotal`.
+
+You can also send line item level data and each line item can have a `description`,
+`qty`, `price`, and `extended` price.
+
+If you fail to send an extended price, BlockChyp will multiply the `qty` by the
+`price`.  However, we strongly recommend you precalculate all the fields yourself
+to ensure consistency.  For example, your treatment of floating-point multiplication and rounding
+may differ slightly from BlockChyp's.
+
+**Discounts**
+
+You have the option to show discounts on the display as individual line items
+with negative values or you can associate discounts with a specific line item.
+You can apply any number of discounts to an individual line item with a description
+and amount.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  test: true,
+  terminalName: 'Test Terminal',
+  transaction: {
+    subtotal: '60.00',
+    tax: '5.00',
+    total: '65.00',
+    items: [
+      {
+        description: 'Leki Trekking Poles',
+        price: '35.00',
+        quantity: 2,
+        extended: '70.00',
+        discounts: [
+          {
+            description: 'memberDiscount',
+            amount: '10.00'
+          }
+        ]
+      }
+    ]
+  }
+}
+
+response = blockchyp.updateTransactionDisplay(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Display Message
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+This API displays a message on the payment terminal.
+
+Just specify the target terminal and the message using the `message` parameter.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  test: true,
+  terminalName: 'Test Terminal',
+  message: 'Thank you for your business.'
+}
+
+response = blockchyp.message(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Boolean Prompt
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+This API Pprompts the customer to answer a yes or no question.
+
+You can specify the question or prompt with the `prompt` parameter and
+the response is returned in the `response` field.
+
+This can be used for a number of use cases including starting a loyalty enrollment
+workflow or customer facing suggestive selling prompts.
+
+**Custom Captions**
+
+You can optionally override the "YES" and "NO" button captions by
+using the `yesCaption` and `noCaption` request parameters.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  test: true,
+  terminalName: 'Test Terminal',
+  prompt: 'Would you like to become a member?',
+  yesCaption: 'Yes',
+  noCaption: 'No'
+}
+
+response = blockchyp.booleanPrompt(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Text Prompt
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+This API prompts the customer to enter numeric or alphanumeric data.
+
+Due to PCI rules, free-form prompts are not permitted when the response
+could be any valid string.  The reason for this is that a malicious
+developer (not you, of course) could use text prompts to ask the customer to
+input a card number or PIN code.
+
+This means that instead of providing a prompt, you provide a `promptType` instead.
+
+The prompt types currently supported are listed below:
+
+* **phone**: Captures a phone number.
+* **email**: Captures an email address.
+* **first-name**: Captures a first name.
+* **last-name**: Captures a last name.
+* **customer-number**: Captures a customer number.
+* **rewards-number**: Captures a rewards number.
+
+You can specify the prompt with the `promptType` parameter and
+the response is returned in the `response` field.
+
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  test: true,
+  terminalName: 'Test Terminal',
+
+  # Type of prompt. Can be 'email', 'phone', 'customer-number', or
+  # 'rewards-number'.
+  promptType: PromptType::EMAIL
+}
+
+response = blockchyp.textPrompt(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### List Terminals
+
+
+
+* **API Credential Types:** Merchant & Partner
+* **Required Role:** Terminal Management
+
+This API returns details about terminals associated with a merchant account.
+
+Status and resource information is returned for all terminals along with a preview of the 
+current branding image displayed on the terminal
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+}
+
+response = blockchyp.terminals(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Deactivate Terminal
+
+
+
+* **API Credential Types:** Merchant & Partner
+* **Required Role:** Terminal Management
+
+This API deactivates a payment terminal.
+
+If the terminal exists and is currently online, it will be removed from the merchant's 
+terminal inventory.  The terminal will be remotely cleared and factory reset.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  terminalId: '<TERMINAL ID>'
+}
+
+response = blockchyp.deactivateTerminal(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Activate Terminal
+
+
+
+* **API Credential Types:** Merchant & Partner
+* **Required Role:** Terminal Management
+
+This API activates a payment terminal.
+
+If successful, the payment terminal will restart, generate new encryption keys, and download any active
+branding assets for the merchant account it's been added to.
+
+Activation requests require an activation code and a unique terminal name.  All terminal names must be unique across
+a merchant account.
+
+Optional Parameters
+
+* **merchantId:** For partner scoped API credentials, a merchant ID is required.  For merchant scoped API credentials, the merchant ID is implicit and cannot be overridden.
+* **cloudRelay:** Activates the terminal in cloud relay mode.
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  terminalName: 'Test Terminal',
+  activationCode: '<ACTIVATION CODE>'
+}
+
+response = blockchyp.activateTerminal(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Reboot Terminal
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+This API reboots the terminal.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  terminalName: 'Test Terminal'
+}
+
+response = blockchyp.reboot(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+### Terms & Conditions Endpoints
+
+
+Developers can use BlockChyp to display and capture acceptance of contracts or agreements related to transactions.
+These agreements can be any long-form contract ranging from rental agreements to HIPPA disclosures.
+
+There are two basic approaches to terms and conditions capture.  Merchants can store contract templates in 
+BlockChyp or they can send the full agreement text as part of every API call.  The right approach will largely 
+depend on whether or not the system being integrated with BlockChyp already has a mechanism for organizing 
+and managing agreements.  For systems that already have this feature built in, it's probably not necessary 
+to use Terms and Conditions.
+
+When agreements are displayed on a terminal, the consumer can scroll through and read the entire agreement,
+and provide a signature.  Results are returned as part of the API response, but BlockChyp also stores a 
+record of the agreement including the signature image, timestamp, and the full text of the agreement that was 
+agreed to.
+
+The Terms and Conditions Log APIs can be used to search and retrieve acceptance records.  Those records
+can also be linked to a transaction if a transaction id is provided with the original API request.
+
+
+
+#### Terms & Conditions Capture
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Terms & Conditions Management
+
+This API allows you to prompt a customer to accept a legal agreement on the terminal
+and (usually) capture their signature.
+
+Content for the agreement can be specified in two ways.  You can reference a
+previously configured T&C template or pass in the full agreement text with every request.
+
+**Using Templates**
+
+If your application doesn't keep track of agreements you can leverage BlockChyp's
+template system.  You can create any number of T&C Templates in the merchant dashboard
+and pass in the `tcAlias` flag to specify which one should display.
+
+**Raw Content**
+
+If your system keeps track of the agreement language or executes complicated merging
+and rendering logic, you can bypass our template system and pass in the full text with
+every transaction.  Use `tcName` to pass in the agreement name and `tcContent` to
+pass in the contract text.  Note that only plain text is supported.
+
+**Bypassing Signatures**
+
+Signature images are captured by default.  If for some reason this doesn't fit your
+use case and you'd like to capture acceptance without actually capturing a signature image, set
+the `disableSignature` flag in the request.
+
+**Terms & Conditions Log**
+
+Every time a user accepts an agreement on the terminal, the signature image (if captured),
+will be uploaded to the gateway.  The image will also be added to the log along with the full text of the
+agreement.  This preserves the historical record in the event that standard agreements
+or templates change over time.
+
+**Associating Agreements with Transactions**
+
+To associate a Terms & Conditions log entry with a transaction, just pass in the
+Transaction ID or Transaction Ref for the associated transaction.
+
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  test: true,
+  terminalName: 'Test Terminal',
+
+  # Alias for a Terms and Conditions template configured in the BlockChyp
+  # dashboard.
+  tcAlias: 'hippa',
+
+  # Name of the contract or document if not using an alias.
+  tcName: 'HIPPA Disclosure',
+
+  # Full text of the contract or disclosure if not using an alias.
+  tcContent: 'Full contract text',
+
+  # File format for the signature image.
+  sigFormat: SignatureFormat::PNG,
+
+  # Width of the signature image in pixels.
+  sigWidth: 200,
+
+  # Whether or not a signature is required. Defaults to true.
+  sigRequired: true
+}
+
+response = blockchyp.termsAndConditions(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### List Templates
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Terms & Conditions Management
+
+This API returns all terms and conditions templates associated with a merchant account.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+}
+
+response = blockchyp.tcTemplates(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Get Template
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Terms & Conditions Management
+
+This API returns as single terms and conditions template.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  templateId: '<TEMPLATE ID>'
+}
+
+response = blockchyp.tcTemplate(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Update Template
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Terms & Conditions Management
+
+This API updates or creates a terms and conditions template.
+
+Terms and conditions templates are fairly simple and essentially consist of a name, content, and alias.
+
+The name is the caption that will be displayed at the top of the screen.  The alias is a code or short
+description that will be used in subsequence API calls to refer to the template.
+
+Content is the full text of the contract or agreement.  Currently, no special formatting or
+merge behavior is supported.  Only plain text is supported.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  alias: 'HIPPA',
+  name: 'HIPPA Disclosure',
+  content: 'Lorem ipsum dolor sit amet.'
+}
+
+response = blockchyp.tcUpdateTemplate(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Delete Template
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Terms & Conditions Management
+
+This API deletes a terms and conditions template.
+
+If a template is deleted, its alias can be reused and any previous Terms & Conditions log entry
+derived from the template being deleted is fully preserved since log entries always include
+a complete independent copy of the agreement text.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  templateId: '<TEMPLATE ID>'
+}
+
+response = blockchyp.tcDeleteTemplate(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Terms & Conditions Log
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Terms & Conditions Management
+
+This API allows developers to search and sort through terms and conditions log entries.
+
+The default API call with no parameters will return the last 250 log entries in descending order.
+
+Optional parameters can be used to filter and query the data set.
+
+* **transactionId:** If provided, returns only those log entries associated with a specific transactions.  Paging and date filters are ignored if this parameter is used.
+* **maxResults:** The max number of results to return in a single page.  Defaults to 250 and 250 is the maximum value.
+* **startIndex** The zero based start index of results within the full result set to return.  Used to advance pages.  For example, if the page size is 10 and you wish to return the second page of results, send a startIndex of 10. 
+* **startDate**: An optional start date for results provided as an ISO 8601 timestamp. (e.g. 2022-05-24T13:51:38+00:00)
+* **endDate**: An optional end date for results provided as an ISO 8601 timestamp. (e.g. 2022-05-24T13:51:38+00:00)
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  logEntryId: '<LOG ENTRY ID>'
+}
+
+response = blockchyp.tcLog(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Terms & Conditions Details
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Terms & Conditions Management
+
+This API returns details for a single terms and conditions log entry.  The `logEntryId` of the record to be returned is the only required parameter.
+
+The signature image is returned as Base 64 encoded binary in the image format specified by the `sigFormat` field. 
+The default format is PNG.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  logEntryId: '<ENTRY ID>'
+}
+
+response = blockchyp.tcEntry(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+### Token Management
+
+
+BlockChyp supports saved payments and recurring payments through the use of tokens.  Tokens can be created
+via the Enroll API or the web tokenizer.  Once created, these tokens can be used for subsequent payments 
+or associated with customer records as saved payment methods.
+
+Tokens are limited to a single merchant by default, but can be shared across an organization for multi-location 
+merchants by special arrangement with BlockChyp.  Contact your BlockChyp rep to setup token sharing.
+
+
+
+#### Enroll
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+This API allows you to tokenize and enroll a payment method in the token
+vault.  You can also pass in customer information and associate the
+payment method with a customer record.
+
+A token is returned in the response that can be used in subsequent charge,
+preauth, and refund transactions.
+
+**Gift Cards and EBT**
+
+Gift Cards and EBT cards cannot be tokenized.
+
+**E-Commerce Tokens**
+
+The tokens returned by the enroll API and the e-commerce web tokenizer
+are the same tokens and can be used interchangeably.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  test: true,
+  terminalName: 'Test Terminal'
+}
+
+response = blockchyp.enroll(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Token Metadata
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+This API retrieves status and metadata information about a token, 
+including any links to customer records.  
+
+This will also return any customer records related to the card
+behind the token.  If the underlying card has been tokenized
+multiple times, all customers related to the card will be returned,
+even if those customer associations are related to other tokens.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  token: '<TOKEN>'
+}
+
+response = blockchyp.tokenMetadata(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Link Token
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+This API links a payment token with a customer record.  Usually this would only be needed
+to reverse a previous unlink operation.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  token: '<TOKEN>',
+  customerId: '<CUSTOMER ID>'
+}
+
+response = blockchyp.linkToken(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Unlink Token
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+This API removes a payment token link from a customer record.
+
+This will remove links between the customer record and all tokens
+for the same underlying card.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  token: '<TOKEN>',
+  customerId: '<CUSTOMER ID>'
+}
+
+response = blockchyp.unlinkToken(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Delete Token
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+This API deletes a payment token from the gateway.  Tokens are automatically deleted if they have not been used
+for a year.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  token: '<TOKEN>'
+}
+
+response = blockchyp.deleteToken(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+### Customer Endpoints
+
+
+These APIs allow developers to create and manage customer records in BlockChyp.  Developers who wish to use
+BlockChyp for tokenized recurring payments can use tokens directly if they have their own customer management
+system.  However, BlockChyp provides additional tools for managing customers and keeping track of a customer's saved
+payment tokens.
+
+In addition, if customer features are used, BlockChyp can detect a payment method associated with an existing
+customer, and return customer data with payment transactions.  This can be used as a passive method to detect
+repeat customers.
+
+
+
+#### Update Customer
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+This API adds or updates a customer record.
+
+If you pass in customer information including `firstName`, `lastName`, `email`,
+or `sms` without any Customer ID or Customer Ref, a new record will
+be created.
+
+If you pass in `customerRef` and `customerId`, the customer record will be updated
+if it exists.
+
+**Customer Ref**
+
+The `customerRef` field is optional, but highly recommended as this allows you
+to use your own customer identifiers instead of storing BlockChyp's Customer IDs
+in your systems.
+
+**Creating Customer Records With Payment Transactions**
+
+If you have customer information available at the time a payment transaction is
+executed, you can pass all the same customer information directly into a payment transaction.  BlockChyp
+will create a customer record at the same time payment is captured.  The advantage of this approach is
+that the customer's payment card is automatically associated with the customer record in a single step.
+If the customer uses the payment card in the future, the customer data will automatically
+be returned.  You won't need to ask the customer to provide any additional information.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  customer: {
+    id: '<CUSTOMER ID>',
+    customerRef: 'Customer reference string',
+    firstName: 'FirstName',
+    lastName: 'LastName',
+    companyName: 'Company Name',
+    emailAddress: 'support@blockchyp.com',
+    smsNumber: '(123) 123-1231'
+  }
+}
+
+response = blockchyp.updateCustomer(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Retrieve Customer
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+With this API, you can retrieve detailed information about a customer record, including saved payment
+methods if available.
+
+Customers can be looked up by `customerId` or `customerRef`.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  customerId: '<CUSTOMER ID>'
+}
+
+response = blockchyp.customer(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Search Customer
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+This API searches the customer database and returns matching results.
+
+Use `query` to pass in a search string and the system will return all results whose
+first or last names contain the query string.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  query: '(123) 123-1234'
+}
+
+response = blockchyp.customerSearch(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Delete Customer
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+This API deletes a customer record.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  customerId: '<CUSTOMER ID>'
+}
+
+response = blockchyp.deleteCustomer(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+### Survey Reference
+
+
+These APIs are used to work with post-transaction surveys and survey data.
+
+Merchants can optionally configure scaled (1-5) or yes/no questions that can be presented to consumers
+after every approved Charge and Preauth transaction.  Surveys do not require any custom programming and
+merchants can simply configure them without the point-of-sale system needing any additional customization.
+
+However, these APIs allow point-of-sale or third-party system developers to integrate survey question configuration
+or result visualization into their own systems.
+
+
+
+#### List Questions
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Survey Management
+
+This API returns all survey questions in the order in which they would be presented on the terminal.
+
+All questions are returned, whether enabled or disabled.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+}
+
+response = blockchyp.surveyQuestions(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Question Details
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Survey Management
+
+This API returns a single survey question with response data.  `questionId` is required.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  questionId: '<QUESTION ID>'
+}
+
+response = blockchyp.surveyQuestion(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Update Question
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Survey Management
+
+This API updates or creates survey questions.  `questionText` and `questionType` are required 
+fields.  The following values are valid for `questionType`.
+
+* **yes_no:** Use for simple yes or no questions.
+* **scaled:** Displays the question with buttons that allow the customer to respond with values from 1 through 5.
+
+Questions are disabled by default.  Pass in `enabled` to enable a question.
+
+The `ordinal` field is used to control the sequence of questions when multiple questions are enabled.  We recommend keeping
+the number of questions minimal.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  id: '<QUESTION ID>',
+  ordinal: 1,
+  questionText: 'Would you shop here again?',
+  questionType: 'yes_no',
+  enabled: true
+}
+
+response = blockchyp.updateSurveyQuestion(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Delete Question
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Survey Management
+
+This API deletes a survey question. `questionId` is a required parameter.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  questionId: '<QUESTION ID>'
+}
+
+response = blockchyp.deleteSurveyQuestion(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Survey Results
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Survey Management
+
+This API returns survey results for a single question.
+
+The results returned include the response rate, which is the percentage of transactions after which
+the consumer provided an answer.
+
+The `responses` array breaks down the results by answer, providing the total number of responses,
+the answer's percentage of the total, and the average transaction amount associated with a specific
+answer.
+
+By default, all results based on all responses are returned.  However, developers may optionally provide 
+`startDate` and `endDate` parameters to return only responses provided between certain dates.
+
+`startDate` and `endDate` can be provided in MM/DD/YYYY or YYYY-MM-DD format.
+
+
+
+
+```ruby
+# frozen_string_literal: true
+
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  questionId: '<QUESTION ID>'
+}
+
+response = blockchyp.surveyResults(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+### Media and Branding Control
+
+
+BlockChyp has a sophisticated terminal media and branding control platform.  Terminals can be configured to
+display logos, images, videos, and slide shows when a terminal is idle.  Branding assets can be configured
+at the partner, organization, and merchant level with fine-grained hour-by-hour schedules, if desired. 
+
+Conceptually, all branding and media start with the media library.  Merchants, Partners, and Organizations can
+upload images or video and build branding assets from uploaded media.
+
+Slide shows can combine images from the media library into a timed loop of repeating images.
+
+Branding Assets can then be used to combine media or slide shows with priority and timing rules to create what 
+we call the Terminal Branding Stack.
+
+We call a group of branding assets the *Terminal Branding Stack* because there are implicit rules about which 
+branding assets take priority. For example, a merchant with no branding assets configured will inherit the 
+branding rules from any organization to which the merchant may belong.  If the merchant doesn't belong to an organization 
+or the organization has no branding rules configured, then the system will defer to branding defaults established 
+by the point-of-sale or software partner that owns the merchant.
+
+This feature enables partners and organizations (multi-store operators and large national chains) to configure branding
+for potentially thousands of terminals from a single interface.
 
-puts "Response: #{response.inspect}"
+Terminal Branding can also be configured at the individual terminal level and a merchant's terminal fleet 
+can be broken into groups and branding configured at the group level.  Branding configured at the terminal
+level will always override branding from any higher level group.
 
+The order of priority for the Terminal Branding Stack is given below.
 
-```
+* Terminal
+* Terminal Group
+* Merchant
+* Organization (Region, Chain, etc)
+* Partner
+* BlockChyp Default Logo
 
-#### Display Message
 
 
+#### Media Library
 
-Displays a message on the payment terminal.
 
-Just specify the target terminal and the message using the `message` parameter.
+
+* **API Credential Types:** Merchant, Partner, & Organization
+* **Required Role:** Media Management
+
+This API returns the entire media library associated with the API Credentials (Merchant, Partner, or Organization).  The media library results will include the ID used
+to reference a media asset in slide shows and branding assets along with the full file url and thumbnail.
 
 
 
@@ -1302,34 +2887,54 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
-  test: true,
-  terminalName: 'Test Terminal',
-  message: 'Thank you for your business.'
 }
 
-response = blockchyp.message(request)
+response = blockchyp.media(request)
 
 puts "Response: #{response.inspect}"
 
 
 ```
 
-#### Boolean Prompt
+#### Upload Media
 
 
 
-Prompts the customer to answer a yes or no question.
+* **API Credential Types:** Merchant, Partner, & Organization
+* **Required Role:** Media Management
 
-You can specify the question or prompt with the `prompt` parameter and
-the response is returned in the `response` field.
+This API supports media library uploads.  The operation of this API works slightly differently depending 
+on the SDK platform.  In all cases, the intent is to allow the file's binary to be passed into the SDK using 
+the lowest level I/O primitive possible in order to support situations where developers aren't working
+with literal files.  It might be (and usually is) more convenient to work with buffers, raw bytes, or streams.
 
-This can be used for a number of use cases including starting a loyalty enrollment
-workflow or customer facing suggestive selling prompts.
+For example, the Go implementation accepts an `io.Reader` and the Java implementation accepts a
+`java.io.InputStream`.  The CLI does accept a literal File URL via the `-file` command line parameter.
 
-**Custom Captions**
+The following file formats are accepted as valid uploads:
 
-You can optionally override the "YES" and "NO" button captions by
-using the `yesCaption` and `noCaption` request parameters.
+* .png
+* .jpg
+* .jpeg
+* .gif
+* .mov
+* .mpg
+* .mp4
+* .mpeg
+
+The UploadMetadata object allows developers to pass additional metadata about the upload including
+`fileName`, `fileSize`, and `uploadId`.
+
+None of these values are required, but providing them can unlock some additional functionality relating to 
+media uploads.  `fileName` will be used to record the original file name in the media library.  `fileSize` 
+and `uploadId` are used to support upload status tracking, which is especially useful for large video file
+uploads.  
+
+The `fileSize` should be the file's full size in bytes.  
+
+The `uploadId` value can be any random string.  This is the value you'll use to check the status of an upload
+via the Upload Status API.  This API will return information needed to drive progress feedback on uploads and 
+return video transcoding information.
 
 
 
@@ -1347,45 +2952,35 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
-  test: true,
-  terminalName: 'Test Terminal',
-  prompt: 'Would you like to become a member?',
-  yesCaption: 'Yes',
-  noCaption: 'No'
+  fileName: 'aviato.png',
+  fileSize: 18843,
+  uploadId: '<RANDOM ID>'
 }
 
-response = blockchyp.booleanPrompt(request)
+file = File.open("aviato.png")
+content = file.read
+response = blockchyp.uploadMedia(request, content)
 
 puts "Response: #{response.inspect}"
 
 
 ```
 
-#### Text Prompt
-
-
+#### Upload Status
 
-Prompts the customer to enter numeric or alphanumeric data.
 
-Due to PCI rules, free form prompts are not permitted when the response
-could be any valid string.  The reason for this is that a malicious
-developer (not you, of course) could use text prompts to ask the customer to
-input a card number or PIN code.
-
-This means that instead of providing a prompt, you provide a `promptType` instead.
 
-The prompt types currently supported are listed below:
+* **API Credential Types:** Merchant, Partner, & Organization
+* **Required Role:** Media Management
 
-* **phone**: Captures a phone number.
-* **email**: Captures an email address.
-* **first-name**: Captures a first name.
-* **last-name**: Captures a last name.
-* **customer-number**: Captures a customer number.
-* **rewards-number**: Captures a rewards number.
+This API returns status and progress information about in progress or recently completed uploads.
 
-You can specify the prompt with the `promptType` parameter and
-the response is returned in the `response` field.
+Before calling this API, developers must first start a file upload with `fileSize` and `uploadId` parameters.
 
+The data structure returned will include the file size, number of bytes uploaded, a narrative status
+and flags indicating whether or not the upload is complete or post upload processing is in progress.  
+If the upload is completed, the ID assigned to the media asset and a link to the thumbnail image will 
+also be returned.
 
 
 
@@ -1403,48 +2998,62 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
-  test: true,
-  terminalName: 'Test Terminal',
-
-  # Type of prompt. Can be 'email', 'phone', 'customer-number', or
-  # 'rewards-number'.
-  promptType: PromptType::EMAIL
+  uploadId: '<UPLOAD ID>'
 }
 
-response = blockchyp.textPrompt(request)
+response = blockchyp.uploadStatus(request)
 
 puts "Response: #{response.inspect}"
 
 
 ```
 
-#### Update Customer
+#### Get Media Asset
 
 
 
-Adds or updates a customer record.
+* **API Credential Types:** Merchant, Partner, & Organization
+* **Required Role:** Media Management
 
-If you pass in customer information including `firstName`, `lastName`, `email`,
-or `sms` without any Customer ID or Customer Ref, a new record will
-be created.
+This API returns a detailed media asset.  The data returned includes the exact same media information returned
+by the full media library endpoint, including fully qualified URLs pointing to the original media file
+and the thumbnail.
 
-If you pass in `customerRef` and `customerId`, the customer record will be updated
-if it exists.
 
-**Customer Ref**
 
-The `customerRef` field is optional, but highly recommended as this allows you
-to use your own customer identifiers instead of storing BlockChyp's Customer IDs
-in your systems.
 
-**Creating Customer Records With Payment Transactions**
+```ruby
+# frozen_string_literal: true
 
-If you have customer information available at the time a payment transaction is
-executed, you can pass all the same customer information directly into a payment transaction and
-create a customer record at the same time payment is captured.  The advantage of this approach is
-that the customer's payment card is automatically associated with the customer record in a single step.
-If the customer uses the payment card in the future, the customer data will automatically
-be returned without needing to ask the customer to provide any additional information.
+require 'blockchyp'
+
+blockchyp = BlockChyp::BlockChyp.new(
+  ENV['BC_API_KEY'],
+  ENV['BC_BEARER_TOKEN'],
+  ENV['BC_SIGNING_KEY']
+)
+
+# Set request parameters
+request = {
+  mediaId: '<MEDIA ASSET ID>'
+}
+
+response = blockchyp.mediaAsset(request)
+
+puts "Response: #{response.inspect}"
+
+
+```
+
+#### Delete Media Asset
+
+
+
+* **API Credential Types:** Merchant, Partner, & Organization
+* **Required Role:** Media Management
+
+This API deletes a media asset.  Note that a media asset cannot be deleted if it is in use in a slide 
+show or in the terminal branding stack.
 
 
 
@@ -1462,32 +3071,26 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
-  customer: {
-    id: 'ID of the customer to update',
-    customerRef: 'Customer reference string',
-    firstName: 'FirstName',
-    lastName: 'LastName',
-    companyName: 'Company Name',
-    emailAddress: 'support@blockchyp.com',
-    smsNumber: '(123) 123-1231'
-  }
+  mediaId: '<MEDIA ASSET ID>'
 }
 
-response = blockchyp.updateCustomer(request)
+response = blockchyp.deleteMediaAsset(request)
 
 puts "Response: #{response.inspect}"
 
 
 ```
 
-#### Retrieve Customer
+#### List Slide Shows
 
 
 
-Retrieves detailed information about a customer record, including saved payment
-methods if available.
+* **API Credential Types:** Merchant, Partner, & Organization
+* **Required Role:** Media Management
 
-Customers can be looked up by `customerId` or `customerRef`.
+This API returns all slide shows.  
+
+Note that slide level data is not returned with this API.   Use the Get Slide Show API to get slide level detail.
 
 
 
@@ -1505,24 +3108,26 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
-  customerId: 'ID of the customer to retrieve'
 }
 
-response = blockchyp.customer(request)
+response = blockchyp.slideShows(request)
 
 puts "Response: #{response.inspect}"
 
 
 ```
 
-#### Search Customer
+#### Get Slide Show
 
 
 
-Searches the customer database and returns matching results.
+* **API Credential Types:** Merchant, Partner, & Organization
+* **Required Role:** Media Management
 
-Use `query` to pass in a search string and the system will return all results whose
-first or last names contain the query string.
+This API returns a single slide show.  Slide level detail is returned with the fully qualified thumbnail URL
+for each slide.
+
+`slideShowId` is the only required parameter.
 
 
 
@@ -1540,25 +3145,31 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
-  query: '(123) 123-1234'
+  slideShowId: '<SLIDE SHOW ID>'
 }
 
-response = blockchyp.customerSearch(request)
+response = blockchyp.slideShow(request)
 
 puts "Response: #{response.inspect}"
 
 
 ```
 
-#### Cash Discount
+#### Update Slide Show
 
 
 
-Calculates the surcharge, cash discount, and total amounts for cash transactions.
+* **API Credential Types:** Merchant, Partner, & Organization
+* **Required Role:** Media Management
 
-If you're using BlockChyp's cash discounting features, you can use this endpoint
-to make sure the numbers and receipts for true cash transactions are consistent
-with transactions processed by BlockChyp.
+This API updates or creates a slide show.  `name`, `delay` and `slides` are required.
+
+The slides property is an array of slides.  The Slide data structure has ordinal and thumbnail URL fields, 
+but these are not required when updating or creating a slide show.  Only the `mediaId` field is required
+when updating or creating a slide show.
+
+When using the CLI, slides can be specified by sending a comma-separated list of media ids via the `-mediaId`
+parameter.
 
 
 
@@ -1576,43 +3187,30 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
-  amount: '100.00',
-  cashDiscount: true,
-  surcharge: true
+  name: 'Test Slide Show',
+  delay: 5,
+  slides: [
+    {
+      mediaId: '<MEDIA ID>'
+    }
+  ]
 }
 
-response = blockchyp.cashDiscount(request)
+response = blockchyp.updateSlideShow(request)
 
 puts "Response: #{response.inspect}"
 
 
 ```
 
-#### Batch History
-
-
-
-This endpoint allows developers to query the gateway for the merchant's batch history.
-The data will be returned in descending order of open date with the most recent
-batch returned first.  The results will include basic information about the batch.
-For more detail about a specific batch, consider using the Batch Details API.
-
-**Limiting Results**
+#### Delete Slide Show
 
-This API will return a maximum of 250 results.  Use the `maxResults` property to
-limit maximum results even further and use the `startIndex` property to
-page through results that span multiple queries.
 
-For example, if you want the ten most recent batches, just pass in a value of
-`10` for `maxResults`.  Also note that `startIndex` is zero based. Use a value of `0` to
-get the first batch in the dataset.
 
-**Filtering By Date Range**
+* **API Credential Types:** Merchant, Partner, & Organization
+* **Required Role:** Media Management
 
-You can also filter results by date.  Use the `startDate` and `endDate`
-properties to return only those batches opened between those dates.
-You can use either `startDate` and `endDate` and you can use date filters
-in conjunction with `maxResults` and `startIndex`
+This API deletes a slide show  `slideShowId` is the only required parameter.
 
 
 
@@ -1630,28 +3228,33 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
-  maxResults: 250,
-  startIndex: 1
+  slideShowId: '<SLIDE SHOW ID>'
 }
 
-response = blockchyp.batchHistory(request)
+response = blockchyp.deleteSlideShow(request)
 
 puts "Response: #{response.inspect}"
 
 
 ```
 
-#### Batch Details
+#### Terminal Branding
 
 
 
-This endpoint allows developers to pull down details for a specific batch,
-including captured volume, gift card activity, expected deposit, and
-captured volume broken down by terminal.
+* **API Credential Types:** Merchant, Partner, & Organization
+* **Required Role:** Media Management
 
-The only required request parameter is `batchId`.  Batch IDs are returned
-with every transaction response and can also be discovered using the Batch
-History API.
+This API returns the full branding stack for a given API scope in the order of priority.
+
+Consumers of this API should pay special attention to the `editable` field.  This field indicates whether or
+not a branding asset is read-only from the perspective of a particular API Credential scope.
+
+The `thumbnail` and `previewImage` attributes can be used to support building user interfaces for
+managing the branding stack. `previewImage` differs from `thumbnail` in that the preview image is 
+intended to show how an asset would actually look when displayed on the terminal.
+
+`activeAsset` returns the asset that is currently visible on the terminal.
 
 
 
@@ -1669,66 +3272,86 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
-  batchId: 'BATCHID'
 }
 
-response = blockchyp.batchDetails(request)
+response = blockchyp.terminalBranding(request)
 
 puts "Response: #{response.inspect}"
 
 
 ```
 
-#### Transaction History
+#### Update Branding Asset
 
 
 
-This endpoint provides a number of different methods to sift through
-transaction history.
+* **API Credential Types:** Merchant, Partner, & Organization
+* **Required Role:** Media Management
 
-By default with no filtering properties, this endpoint will return the 250
-most recent transactions.
+This API updates or creates a single Branding Asset.
 
-**Limiting Results**
+Branding Assets represent a single element of the terminal branding stack.  A Branding Asset can be a video or image,
+in which case a `mediaId` referencing an asset from the media library must be provided.  A Branding Asset can also
+be a slide show, in which case `slideShowId` must be provided.  Branding Assets must have a valid `mediaId` or a valid
+`slideShowId`.  The optional `notes` field can be used to provide short notes and descriptions for a Branding asset.
 
-This API will return a maximum of 50 results in a single query.  Use the `maxResults` property
-to limit maximum results even further and use the `startIndex` property to
-page through results that span multiple queries.
+**Visibility Flags**
 
-For example, if you want the ten most recent batches, just pass in a value of
-`10` for `maxResults`.  Also note that `startIndex` is zero based. Use a value of `0` to
-get the first transaction in the dataset.
+In order for a Branding Asset to be visible on a terminal, the `enabled` flag must be set to true and the `preview`
+must be turned off.  `preview` is intended to show how a proposed Branding Asset will behave
+without pushing it to live terminals.  The Publish button in the BlockChyp merchant portal effectively turns
+the `preview` setting off.
 
-**Filtering By Date Range**
+**Order and Sequencing**
 
-You can also filter results by date.  Use the `startDate` and `endDate`
-properties to return only transactions run between those dates.
-You can use either `startDate` or `endDate` and you can use date filters
-in conjunction with `maxResults` and `startIndex`
+The `ordinal` field is used to specify priority for a Branding Asset.  Assets with a higher value for `ordinal`
+will be prioritized first.
 
-**Filtering By Batch**
+**Padding Images**
 
-To restrict results to a single batch, pass in the `batchId` parameter.
+For plain images, it's sometimes helpful to add margins to images.  This is especially helpful with logos
+or any image file rendered without any white space or margins between the image content and edge of the image file.
+Set the `padded` flag to true if you'd like BlockChyp to auto apply margins when displaying an image on 
+the terminal.
 
-**Filtering By Terminal**
+**Scheduling**
 
-To restrict results to those executed on a single terminal, just
-pass in the terminal name.
+By default, a Branding Asset placed on top of the Branding Stack, if it's `enabled` and not in `preview`
+mode, will immediately be displayed on the terminal round the clock.
 
-**Combining Filters**
+Branding Assets can be scheduled with effective start and stop dates for seasonal campaigns.  These assets can
+also be scheduled for specific times of day and specific days of the week.
 
-None of the above filters are mutually exclusive.  You can combine any of the
-above properties in a single request to restrict transaction results to a
-narrower set of results.
+* **startDate:** Optional date after which the Branding Asset is eligible for display.  Can be provided in MM/DD/YYYY or YYYY-MM-DD format.
+* **endDate:** Optional date before which the Branding Asset is eligible for display.  Can be provided in MM/DD/YYYY or YYYY-MM-DD format.
+* **startTime** Optional time of day after which the branding asset is eligible for display.  Must be provided in 24 hour time: HH:MM.
+* **endTime** Optional time of day before which the branding asset is eligible for display.  Must be provided in 24 hour time format: HH:MM
+* **daysOfWeek** For branding assets that should only be displayed on certain days of the week, this field is an array of day of the week constants. (Constants vary by SDK platform.)
 
-**Searching Transaction History**
+**Read Only Fields**
 
-You can search transaction history by passing in search criteria with the 
-`query` option.  The search system will match on amount (requested and authorized),
-last four of the card number, cardholder name, and the auth code.
+The Branding Asset data structure has a number of read only fields that are returned when Branding Assets are 
+retrieved.  But these fields are ignored when you try to send them as part of an update.  These are derived
+or calculated fields and are helpful for displaying branding assets in a management user interface, but 
+cannot be changed via an API call.
 
-Note that when search queries are used, terminalName or 
-batch id filters are not supported.
+These fields are:
+
+* ownerId
+* merchantId
+* organizationId
+* partnerId
+* userId
+* userName
+* thumbnail
+* lastModified
+* editable
+* assetType
+* ownerType
+* ownerTypeCaption
+* previewImage
+* narrativeEffectiveDates
+* narrativeDisplayPeriod
 
 
 
@@ -1746,23 +3369,36 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
-  maxResults: 10
+  mediaId: '<MEDIA ID>',
+  padded: true,
+  ordinal: 10,
+  startDate: '01/06/2021',
+  startTime: '14:00',
+  endDate: '11/05/2024',
+  endTime: '16:00',
+  notes: 'Test Branding Asset',
+  preview: false,
+  enabled: true
 }
 
-response = blockchyp.transactionHistory(request)
+response = blockchyp.updateBrandingAsset(request)
 
 puts "Response: #{response.inspect}"
 
 
 ```
 
-#### Merchant Profile
+#### Delete Branding Asset
 
 
 
-Returns detailed metadata about the merchant's configuraton, including
-basic identity information, terminal settings, store and forward settings,
-and bank account information for merchants that support split settlement.
+* **API Credential Types:** Merchant, Partner, & Organization
+* **Required Role:** Media Management
+
+This API deletes a Branding Asset from the branding stack.
+
+Note that deleting a Branding Asset does not delete the underlying media from the media library or slide
+show from the slide show library.
 
 
 
@@ -1780,22 +3416,101 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
+  assetId: '<BRANDING ASSET ID>'
 }
 
-response = blockchyp.merchantProfile(request)
+response = blockchyp.deleteBrandingAsset(request)
 
 puts "Response: #{response.inspect}"
 
 
 ```
 
-#### List Queued Transactions
+### Merchant Management
 
 
+These APIs allow partners to manage and configure their merchant portfolios.
+
+Use of these APIs (other than the Merchant Profile API) requires partner scoped API credentials
+with special roles and permissions that may require a special arrangement with BlockChyp.
+
+For example, Partners usually can't board merchants directly, but must board merchants using
+the standard underwriting process via offer codes and invitations.
 
-Returns a list of transaction refs of transactions queued on a terminal.
-Details about the transactions can be retrieved using the Transaction Status
-API.
+
+
+#### Merchant Profile
+
+
+
+* **API Credential Types:** Merchant
+* **Required Role:** Payment API Access
+
+The API returns detailed metadata about the merchant's configuration, including
+basic identity information, terminal settings, store and forward settings,
+and bank account information for merchants that support split settlement.
+
+Some of these fields can be updated via the Update Merchant API, but many of these
+fields are controlled by underwriting and cannot be altered outside of the 
+underwriting and risk processes.
+
+**Merchant Descriptive Fields**
+
+The following fields are basic descriptive fields that can be used to describe and identify merchants.
+
+* **companyName:** The merchant's official corporate entity name.
+* **dbaName:** The business's DBA (doing business as) name.
+* **contactName:** Name of the merchant's primary control contact.
+* **contactNumber:** Primary control contact's phone number.
+* **locationName:** Optional location name for multi-location operators.
+* **storeNumber:** Optional store number for multi-location operators.
+* **partnerRef:** Optional reference number partners can add to a merchant record.  Usually the partner's own identifier for the merchant.
+* **timeZone:** Unix style local time zone for the merchant. Example: America/New_York.
+* **publicKey:** Read only field.  The merchant's blockchain public key.  Generated and assigned when a merchant account is first created.
+* **billingAddress:** Address for billing and written correspondence.
+* **shippingAddress:** Physical shipping address. Usually the actual street address of the business.
+* **status:** Current status of the merchant account.
+* **tcDisabled:** Disables all terms and conditions features in the merchant dashboard.  Used to hide the feature if a partner has not chosen to support it.
+* **gatewayOnly:** Indicates that a merchant has been boarded in gateway only mode.  Not common.
+
+**Batch and Terminal Settings**
+
+The following fields are used to control batch closure and high level terminal configuration.
+
+* **batchCloseTime:** Time in 24 hour HH:MM format when batches will automatically close in the merchant's local time.  Defaults to 3 AM.
+* **autoBatchClose:** Flag the determines whether or not batches will automatically close.  Defaults to true.
+* **disableBatchEmails:** Flag that optionally turns off automatic batch closure notification emails.
+* **cooldownTimeout:** The amount of time in seconds after a transactions for which the transaction response is displayed on the terminal.  After the cooldown period elapses, the terminal will revert to the idle state and display the currently active terminal branding.
+* **surveyTimeout:** The amount of time in seconds a survey question should be displayed on a terminal before reverting to the idle screen.
+* **pinEnabled:** Enables pin code entry for debit cards, EBT cards, and EMV cards with pin CVMs.  Will be ignored if terminals are not injected with the proper encryption keys.
+* **pinBypassEnabled:** Enable pin bypass for debit transactions.
+* **cashBackEnabled:** Enables cash back for debit transactions.
+* **cashbackPresets:** An array of four default values for cashback amounts when cashback is enabled.
+* **storeAndForwardEnabled:** Enables automatic store and forward during network outages.  Store and Forward does not support cash back, refunds, EBT, or gift card transactions.
+* **storeAndForwardFloorLimit:** Maximum dollar value of a store and forward transaction.
+* **ebtEnabled:** Enables EBT (SNAP) on BlockChyp terminals.
+* **tipEnabled:** Enables tips entry on the terminal.
+* **promptForTip:** If true, the terminal will always prompt for a tip, even if the API call does not request a tip prompt.
+* **tipDefaults:** An array of exactly three percentages that will be used to calculate default tip amounts.
+* **giftCardsDisabled:** Disables BlockChyp gift cards.  Normally only used if the merchant is using an alternate gift card system.
+* **digitalSignaturesEnabled:** Enables electronic signature capture for mag stripe cards and EMV cards with Signature CVMs.
+* **digitalSignatureReversal:** Will cause a transaction to auto-reverse if the consumer refuses to provide a signature.
+* **manualEntryEnabled:** Enables manual card entry.
+* **manualEntryPromptZip:** Requires zip code based address verification for manual card entry.
+* **manualEntryPromptStreetNumber:** Requires street/address based verification for manual card entry.
+
+**Card Brand and Transaction Settings**
+
+* **freeRangeRefundsEnabled:** Enables direct refunds that do not reference a previous transaction.
+* **partialAuthEnabled:** Indicates that partial authorizations (usually for gift card support) are enabled.
+* **splitBankAccountsEnabled:** Used for law firm merchants only.
+* **contactlessEmv:** Enables contactless/tap transactions on a terminal.  Defaults to true.
+* **visa:** Enables Visa transactions.
+* **masterCard:** Enables MasterCard transactions.
+* **amex:** Enables American Express transactions.
+* **discover:** Enables Discover transactions.
+* **jcb:** Enables JCB (Japan Card Bureau) transactions.
+* **unionPay:** Enables China UnionPay transactions.
 
 
 
@@ -1813,23 +3528,29 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
-  terminalName: 'Test Terminal'
 }
 
-response = blockchyp.listQueuedTransactions(request)
+response = blockchyp.merchantProfile(request)
 
 puts "Response: #{response.inspect}"
 
 
 ```
 
-#### Delete Queued Transaction
+#### Get Merchants
 
 
 
-Deletes one or all queued transactions from a terminal. If `*` is passed as
-a transaction ref, then the entire terminal queue will be cleared. An error is
-returned if the passed transaction ref is not queued on the terminal.
+* **API Credential Types:** Partner & Organization
+* **Required Role:** Merchant Management
+
+This is a partner or organization level API that can be used to return the merchant portfolio.
+
+Live merchants are returned by default.  Use the `test` flag to return only test merchants.  The 
+results returned include detailed settings including underwriting controlled flags.
+
+A maximum of 250 merchants are returned by default.  For large merchant portfolios, the `maxResults`
+and `startIndex` field can be used to reduce the page size and page through multiple pages of results.
 
 
 
@@ -1847,22 +3568,87 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
-  terminalName: 'Test Terminal',
-  transactionRef: '*'
+  test: true
 }
 
-response = blockchyp.deleteQueuedTransaction(request)
+response = blockchyp.getMerchants(request)
 
 puts "Response: #{response.inspect}"
 
 
 ```
 
-#### Delete Customer
+#### Update Merchant
+
+
+
+* **API Credential Types:** Merchant, Partner, & Organization
+* **Required Role:** Merchant Management
+
+This API can be used to update or create merchant accounts.
+
+Merchant scoped API credentials can be used to update merchant account settings.
+
+Partner scoped API credentials can be used to update merchants, create new test 
+merchants or board new gateway merchants.
+
+**Merchant Descriptive Fields**
 
+The following fields are basic descriptive fields that can be used to describe and identify merchants.
 
+* **companyName:** The merchant's official corporate entity name.
+* **dbaName:** The businesses DBA (doing business as) name.
+* **contactName:** Name of the merchant's primary control contact.
+* **contactNumber:** Primary control contact's phone number.
+* **locationName:** Optional location name for multi location operators.
+* **storeNumber:** Optional store number for multi location operators.
+* **partnerRef:** Optional reference number partners can add to a merchant record.  Usually the partner's own identifier for the merchant.
+* **timeZone:** Unix style local time zone for the merchant. Example: America/New_York.
+* **publicKey:** Read only field.  The merchant's blockchain public key.  Generated and assigned when a merchant account is first created.
+* **billingAddress:** Address for billing and written correspondence.
+* **shippingAddress:** Physical shipping address. Usually the actual street address of the business.
+* **status:** Current status of the merchant account.
+* **tcDisabled:** Disables all terms and conditions features in the merchant dashboard.  Used to hide the feature if a partner has not chosen to support it.
+* **gatewayOnly:** Indicates that a merchant has been boarded in gateway only mode.  Not common.
 
-Deletes a customer record.
+**Batch and Terminal Settings**
+
+The following fields are used to control batch closure and high level terminal configuration.
+
+* **batchCloseTime:** Time in 24 hour HH:MM format when batches will automatically close in the merchant's local time.  Defaults to 3 AM.
+* **autoBatchClose:** Flag the determines whether or not batches will automatically close.  Defaults to true.
+* **disableBatchEmails:** Flag that optionally turns off automatic batch closure notification emails.
+* **cooldownTimeout:** The amount of time in seconds after a transactions for which the transaction response is displayed on the terminal.  After the cooldown period elapses, the terminal will revert to the idle state and display the currently active terminal branding.
+* **surveyTimeout:** The amount of time in seconds a survey question should be displayed on a terminal before reverting to the idle screen.
+* **pinEnabled:** Enables pin code entry for debit cards, EBT cards, and EMV cards with pin CVMs.  Will be ignored if terminals are not injected with the proper encryption keys.
+* **pinBypassEnabled:** Enable pin bypass for debit transactions.
+* **cashBackEnabled:** Enables cash back for debit transactions.
+* **cashbackPresets:** An array of four default values for cashback amounts when cashback is enabled.
+* **storeAndForwardEnabled:** Enables automatic store and forward during network outages.  Store and Forward does not support cash back, refunds, EBT, or gift card transactions.
+* **storeAndForwardFloorLimit:** Maximum dollar value of a store and forward transaction.
+* **ebtEnabled:** Enables EBT (SNAP) on BlockChyp terminals.
+* **tipEnabled:** Enables tips entry on the terminal.
+* **promptForTip:** If true, the terminal will always prompt for a tip, even if the API call does not request a tip prompt.
+* **tipDefaults:** An array of exactly three percentages that will be used to calculate default tip amounts.
+* **giftCardsDisabled:** Disables BlockChyp gift cards.  Normally only used if the merchant is using an alternate gift card system.
+* **digitalSignaturesEnabled:** Enables electronic signature capture for mag stripe cards and EMV cards with Signature CVMs.
+* **digitalSignatureReversal:** Will cause a transaction to auto-reverse if the consumer refuses to provide a signature.
+* **manualEntryEnabled:** Enables manual card entry.
+* **manualEntryPromptZip:** Requires zip code based address verification for manual card entry.
+* **manualEntryPromptStreetNumber:** Requires street/address based verification for manual card entry.
+
+**Card Brand and Transaction Settings**
+
+* **freeRangeRefundsEnabled:** Enables direct refunds that do not reference a previous transaction.
+* **partialAuthEnabled:** Indicates that partial authorizations (usually for gift card support) are enabled.
+* **splitBankAccountsEnabled:** Used for law firm merchants only.
+* **contactlessEmv:** Enables contactless/tap transactions on a terminal.  Defaults to true.
+* **visa:** Enables Visa transactions.
+* **masterCard:** Enables MasterCard transactions.
+* **amex:** Enables American Express transactions.
+* **discover:** Enables Discover transactions.
+* **jcb:** Enables JCB (Japan Card Bureau) transactions.
+* **unionPay:** Enables China UnionPay transactions.
 
 
 
@@ -1880,21 +3666,33 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
-  customerId: 'ID of the customer to delete'
+  merchantId: '<MERCHANT ID>',
+  test: true,
+  dbaName: 'Test Merchant',
+  companyName: 'Test Merchant',
+  billingAddress: {
+    address1: '1060 West Addison',
+    city: 'Chicago',
+    stateOrProvince: 'IL',
+    postalCode: '60613'
+  }
 }
 
-response = blockchyp.deleteCustomer(request)
+response = blockchyp.updateMerchant(request)
 
 puts "Response: #{response.inspect}"
 
 
 ```
 
-#### Delete Token
+#### Merchant Users
 
 
 
-Deletes a payment token from the gateway.
+* **API Credential Types:** Partner & Organization
+* **Required Role:** Merchant Management
+
+This API returns all users and pending invites associated with a merchant account including any assigned role codes.
 
 
 
@@ -1912,27 +3710,31 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
-  token: 'Token to delete'
+  merchantId: '<MERCHANT ID>'
 }
 
-response = blockchyp.deleteToken(request)
+response = blockchyp.merchantUsers(request)
 
 puts "Response: #{response.inspect}"
 
 
 ```
 
-#### Token Metadata
+#### Invite Merchant User
 
 
 
-Retrieves status and metadata information about a token, 
-including any links to customer records.  
+* **API Credential Types:** Partner & Organization
+* **Required Role:** Merchant Management
 
-This will also return any customer records related to the card
-behind the token.  If the underlying card has been tokenized
-multiple times, all customers related to the card will be returned,
-even if those customer associations are related to other tokens.
+Invites a new user to join a merchant account.  `email`, `firstName`, and `lastName` are required.
+
+The user will be sent an invite email with steps for creating a BlockChyp account and linking it to
+a merchant account.  If the user already has a BlockChyp user account, the new user signup wil be skipped
+and the existing user account will be linked to the merchant account.
+
+Developers can optionally restrict the user's access level by sending one or more role codes.
+Otherwise, the user will be given the default merchant user role. (STDMERCHANT)
 
 
 
@@ -1950,22 +3752,27 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
-  token: 'Token to retrieve'
+  email: 'Email address for the invite'
 }
 
-response = blockchyp.tokenMetadata(request)
+response = blockchyp.inviteMerchantUser(request)
 
 puts "Response: #{response.inspect}"
 
 
 ```
 
-#### Link Token
+#### Add Test Merchant
 
 
 
-Links a payment token with a customer record.  Usually this would only be used
-to reverse a previous unlink operation.
+* **API Credential Types:** Partner
+* **Required Role:** Merchant Management
+
+This is a partner level API that can be used to create test merchant accounts.  This creates
+a basic test merchant with default settings.
+
+Settings can be changed by using the Update Merchant API.
 
 
 
@@ -1983,25 +3790,25 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
-  token: 'Token to link',
-  customerId: 'Customer to link'
+  dbaName: 'DBA Name',
+  companyName: 'Corporate Entity Name'
 }
 
-response = blockchyp.linkToken(request)
+response = blockchyp.addTestMerchant(request)
 
 puts "Response: #{response.inspect}"
 
 
 ```
 
-#### Unlink Token
+#### Delete Test Merchant
 
 
 
-Removes a payment token link from a customer record.
+* **API Credential Types:** Partner
+* **Required Role:** Merchant Management
 
-This will remove links between the customer record and all tokens
-for the same underlying card.
+This partner API can be used to delete unused test merchant accounts. `merchantId` is a required parameter.
 
 
 
@@ -2019,17 +3826,20 @@ blockchyp = BlockChyp::BlockChyp.new(
 
 # Set request parameters
 request = {
-  token: 'Token to unlink',
-  customerId: 'Customer to unlink'
+  merchantId: '<MERCHANT ID>'
 }
 
-response = blockchyp.unlinkToken(request)
+response = blockchyp.deleteTestMerchant(request)
 
 puts "Response: #{response.inspect}"
 
 
 ```
 
+
+
+
+
 ## Running Integration Tests
 
 If you'd like to run the integration tests, create a new file on your system