Abstract: The present disclosure involves detecting a first language type of a query configured to access a column in a data table, wherein the query is requested by a user; converting, by the computing device, the query from the first language type to a second language type that conforms with the data storage format of the data table; after converting the query to the second language type, generating, by the computing device, a temporary table including the column and enforcing an access permission by formatting the temporary table to support the second language type and excluding a row from the temporary table for which the user does not have access rights; and executing, by the computing device, the query against the temporary table to generate a query result.

Abstract: A system may receive a query configured to access a column in a data table. The data table may be in a flat file in a big data storage format. The system may detect the language type of the query and validate the query against the syntax of the language type. The system may also validate an access permission for data in the data table. The access permission may be stored in a permissions database. The system may generate a temporary table including the column with the temporary table configured to support the language type. The system may execute the query against the temporary table to generate a query result based on the temporary table as though it were the underlying data table. The system may enforce column-level or row-level access permissions by excluding columns or rows from the temporary table.

Abstract: The present disclosures presents system and methods for blockchain based payment networks. One such method comprises preparing, by a payment network, a request to complete a transaction from an digital currency account associated with a payer digital wallet for entry on a blockchain ledger, wherein the request to complete the transaction includes an amount and a payee address associated with a fiat currency account; sending the request to complete the transaction to the blockchain ledger; approving the request to complete the transaction; and adjusting a balance of the payer digital wallet and a balance of the fiat currency account in response to approval of the request to complete the transaction by writing the transaction comprising the amount and the payee address to the blockchain ledger, wherein a value of the digital currency substantially matches a value of the fiat currency.

Abstract: A payment network is operated with a blockchain-based ledger. In one embodiment, a request is prepared to complete a transaction from an account associated with a payer digital wallet for entry on a blockchain. The request includes an amount and a payee identifier associated with a payee digital wallet. The request is sent to the blockchain and approved. A balance of the payer digital wallet and a balance of the payee digital wallet are adjusted in response to approval of the request to complete the transaction by at least writing a portion of data associated with the transaction comprising the amount and the payee identifier to the blockchain. A reputation ledger associated with the account is recorded in the blockchain in association with the transaction. The reputation ledger includes at least one reputation score associated with at least one previous transaction conducted by the account.

Abstract: A proof-of-payment system that allows smart connected devices to confirm a payment information. In one example, a smart connected device that comprises a computing device and program instructions. The program instructions, when executed by the processor, cause the computing device to at least retrieve an encrypted proof-of-payment (PoP) payload from a blockchain and decrypt the encrypted PoP payload to retrieve a first identifier from the encrypted PoP payload. The first identifier from the decrypted PoP payload is matched to a second identifier presented at the smart connected device. An action is triggered in response to the first identifier from the encrypted PoP payload matching the second identifier presented at the smart connected device.

Abstract: A blockchain-based loyalty point system that comprises a host computing device for interfacing with authorized devices and loyalty partner websites in a loyalty point network. In one example, the loyalty point network includes a blockchain network and a host computing device. The host computing device is configured to receive a registration request from a client device for access to the loyalty point network. The host computing device causes a registration proposal for the client device to be written to the blockchain network and receives a point adjustment request from a loyalty partner website. The host computing device executes a smart contract in response to receiving the point adjustment request from the loyalty partner website, and the smart contract is executed to adjust the account balance of the customer account based at least in part on the point adjustment request.

Abstract: A proof-of-payment system may receive a payment confirmation including a transaction amount and a merchant identifier. The system may select a record from a registration repository by matching the merchant identifier to the record. The record may have a public key associated with the merchant identifier via a registration process, for example. The system may also generate a proof-of-payment payload comprising an identifier and a payment amount, and encrypt the proof-of-payment payload using the public key. The system may write the encrypted proof-of-payment payload to a blockchain maintained on a first blockchain node.

Abstract: A blockchain-based loyalty point system may include a blockchain API host that receives a request to transfer an amount of loyalty points from a first customer account to a second customer account. The system may validate the request by performing a cryptographic operation on the request using a public key associated with the first customer account. The system may also propagate a proposal to consensus participants for writing to a blockchain, wherein the proposal comprises the first customer account, the second customer account, and the amount of loyalty points. The system may also receive an exchange request from a loyalty wallet associated with the second customer account, validate the exchange request by performing the cryptographic operation on the exchange request using a public key, and propagate an exchange proposal to the consensus participants for writing to the blockchain.

Abstract: A payment network is operated with a blockchain-based ledger. In one embodiment, a request is prepared to complete a transaction from an account associated with a payer digital wallet for entry on a blockchain. The request includes an amount and a payee identifier associated with a payee digital wallet. The request is sent to the blockchain and approved. A balance of the payer digital wallet and a balance of the payee digital wallet are adjusted in response to approval of the request to complete the transaction by at least writing a portion of data associated with the transaction comprising the amount and the payee identifier to the blockchain. A reputation ledger associated with the account is recorded in the blockchain in association with the transaction. The reputation ledger includes at least one reputation score associated with at least one previous transaction conducted by the account.

Abstract: A system for operating a payment network with a blockchain-based ledger may prepare a request to complete a transaction from an account associated with a payer digital wallet for entry on the blockchain. The request may include an amount and payee address associated with a payee digital wallet. The system may also send the request to the blockchain using a blockchain interface. The system may approve or decline the request. The system may further adjust a balance of the payer a balance of the payee to reflect approval of the request. The adjustment may include writing the transaction to the blockchain.

Abstract: A system receives a source and a metadata layer that describes the source. The source may comprise source records with fields containing source data, and the metadata layer may include metadata comprising at least one of a field data type, a field data length, a field description, or a record length. The processor may further validate the metadata layer against the source and write results to a log. The processor may further be configured for transforming the source records into transformed records for a load ready file. The processor may further balance a number of records in the source against a number of transformed records in the load ready file to generate a transformation failure rate.

Abstract: A system may read an input file having an input file size and including a first record and a second record. The first and second record may each have a record length. The system may parse the input file into a first split file and a second split file, with the first split file including the first record and the second split file including the second record. The system may distribute the first split file to a first node to generate a first output file and the second split file to a second node to generate a second output file. Any number of additional split files may be distributed to generate any number output files. The system may combine the output files to generate a converted data file.

Abstract: A blockchain-based loyalty point system may include a blockchain API host that receives a request to transfer an amount of loyalty points from a first customer account to a second customer account. The system may validate the request by performing a cryptographic operation on the request using a public key associated with the first customer account. The system may also propagate a proposal to consensus participants for writing to a blockchain, wherein the proposal comprises the first customer account, the second customer account, and the amount of loyalty points. The system may also receive an exchange request from a loyalty wallet associated with the second customer account, validate the exchange request by performing the cryptographic operation on the exchange request using a public key, and propagate an exchange proposal to the consensus participants for writing to the blockchain.

Abstract: A system may receive a query configured to access a column in a data table. The data table may be in a flat file in a big data storage format. The system may detect the language type of the query and validate the query against the syntax of the language type. The system may also validate an access permission for data in the data table. The access permission may be stored in a permissions database. The system may generate a temporary table including the column with the temporary table configured to support the language type. The system may execute the query against the temporary table to generate a query result based on the temporary table as though it were the underlying data table. The system may enforce column-level or row-level access permissions by excluding columns or rows from the temporary table.

Abstract: Systems and methods of securely storing and retrieving data are disclosed. A database may include a table of data with rows and columns and encrypted at rest. The data may be desired to be accessed by users. However, each user may have different access permissions and each row or column may have different characteristics, such as encryption, data type, and/or the like. As such, access to the data may be controlled in according to the characteristics of the data, the access permissions of the user, and/or the encryption of the data.

Abstract: A system may receive a query configured to access a column in a data table. The data table may be in a flat file in a big data storage format. The system may detect the language type of the query and validate the query against the syntax of the language type. The system may also validate an access permission for data in the data table. The access permission may be stored in a permissions database. The system may generate a temporary table including the column with the temporary table configured to support the language type. The system may execute the query against the temporary table to generate a query result based on the temporary table as though it were the underlying data table. The system may enforce column-level or row-level access permissions by excluding columns or rows from the temporary table.

Abstract: A proof-of-payment system may receive a payment confirmation including a transaction amount and a merchant identifier. The system may select a record from a registration repository by matching the merchant identifier to the record. The record may have a public key associated with the merchant identifier via a registration process, for example. The system may also generate a proof-of-payment payload comprising an identifier and a payment amount, and encrypt the proof-of-payment payload using the public key. The system may write the encrypted proof-of-payment payload to a blockchain maintained on a first blockchain node.

Abstract: Systems and methods of securely storing and retrieving data are disclosed. A database may include a table of data with rows and columns and encrypted at rest. The data may be desired to be accessed by users. However, each user may have different access permissions and each row or column may have different characteristics, such as encryption, data type, and/or the like. As such, access to the data may be controlled in according to the characteristics of the data, the access permissions of the user, and/or the encryption of the data.

Abstract: Systems and methods of securely storing and retrieving data are disclosed. A database may include a table of data with rows and columns and encrypted at rest. The data may be desired to be accessed by users. However, each user may have different access permissions and each row or column may have different characteristics, such as encryption, data type, and/or the like. As such, access to the data may be controlled in according to the characteristics of the data, the access permissions of the user, and/or the encryption of the data.

Abstract: A system for operating a payment network with a blockchain-based ledger may prepare a request to complete a transaction from an account associated with a payer digital wallet for entry on the blockchain. The request may include an amount and payee address associated with a payee digital wallet. The system may also send the request to the blockchain using a blockchain interface. The system may approve or decline the request. The system may further adjust a balance of the payer a balance of the payee to reflect approval of the request. The adjustment may include writing the transaction to the blockchain.