SharedLABS reimagines payments and creates a disruptive new Digital Payments Platform

JACKSONVILLE, Fla., Sept. 4, 2018 /PRNewswire/ —SharedLABS, Inc. (“SharedLABS”), a global software and technology services company focused on delivering digital transformation, has entered into an agreement to help their new client, a global payments technology company, reimagine how companies and individuals make and receive payments to vendors, employees, and sub-contractors, by creating a digital disbursement solution that leverages new hyper ledger technologies in a new way which can dramatically transform operations, customer satisfaction, and cash disbursement, while eliminating billing errors and accelerating payment time.

SharedLABS reimagines payments and creates a disruptive new Digital Payments Platform

Across industries and geographies, the growth of the “gig economy” has brought with it the introduction of countless new methods to make or receive a payment, while adding significant cost and friction to the B2C disbursement process, frustrating workers, vendors, and customers, while tying up cash in accounts receivable, delaying payments, and increasing costs. SharedLABS has been selected by a new client to create a solution which optimizes its deep expertise in payments and technology with hundreds of large multinational enterprises – and incorporates SharedLABS’ own Solutions Suite which consists of Proven Register, allowing various internal and external stakeholders to easily and transparently share data among any number of systems, in an intrinsically secure, mobile-first model, making it infinitely scalable.

This solution offers a nified Payments Platform which extends numerous alternative payment mechanisms for funding consumer recipients, as well as a single integration point, which unlocks multiple funding options and allows its customers to connect via batch file load, web-based applications and API while delivering payments via multiple methods including same day ACH, Cash, PayPal, Push to Debit, Open and Closed Stored Value Cards. The platform has built-in 1099 IRS compliance for reporting and filing, and a sophisticated rules engine for corporations to manage how, when and under what conditions recipients get paid. The platform’s disruptive approach to payments has the potential to dramatically enhance cash flow performance, reduce revenue leakage from disputes, and lower costs.

“Industry disruption is making cycle times for payments irrelevant. The companies who harness the power of digital technologies to transform processes, improve billing and payments quality while reducing latency, and improve security with better accuracy and visibility, will be the frontrunners in platform selection,”said Jason Cory, SharedLABS CEO. SharedLABS’ domain expertise in Payments, FinTech, and emerging technologies – coupled with our proven capabilities developing digital solutions for banking and technology organizations – gives us valuable insights that help CFOs and their teams improve cash flow, operating profits, and customer experiences at an accelerated pace and in a predictable manner.” John Andrews, SharedLABS COO, while speaking about the project, said, “Our experience in creating software products, for software companies using our ESP™ methodology, made us a frontrunner in the highly competitive process our client used to select the successful partner.”

While initially conceptualized to support payments chain of provenance for asset management, SharedLABS is working to extend its hyper ledger and proven register solution’s massively scalable platform to bring transformational value across to Payments, Banking, Retail, Government, Transportation and Logistics, Technology and Telecommunications organizations. As part of its strategy to drive both digitally enabled innovation for its clients, SharedLABS leverages its ESP™ approach, which models plans from concept to cashflow by combining technology and design thinking methodologies, leading digital technology and analytics, and deep domain and vertical expertise to develop solutions which generate significant business impact to help its clients create sustainable competitive advantage.

About SharedLABS, Inc.

Headquartered in Jacksonville, Florida, SharedLABS is a global software and technology services company providing a broad range of software, digital, cloud, and security services to both commercial and government clients which enable businesses to innovate and compete in today’s competitive marketplaces. A respected partner to many of the largest technology companies in the world, SharedLABS creates, supports, implements, and manages the software, infrastructure, and e-commerce systems which drive today’s digital world.

(PRNewsfoto/SharedLabs, Inc.)

Cision View original content with multimedia:https://www.prnewswire.com/news-releases/sharedlabs-reimagines-payments-and-creates-a-disruptive-new-digital-payments-platform-300706588.html

SOURCE SharedLABS, Inc.

Related:

  • No Related Posts

7023012: Security Scan Indicates Support for TLS 1.0 as a Vulnerability

This document (7023012) is provided subject to the disclaimer at the end of this document.

Environment

Verastream Host Integrator 7.7 Service Pack 1
Nessus Professional Security Scan (Tenable Software, Inc.)

Situation

  • A security scanner utility such as Nessus Professional has identified that TCP/IP port 8443 on your Verastream Host Integrator (VHI) server allows TLS 1.0 encryption for connections.
  • Your organization has a policy that only TLS 1.2 will be allowed for production servers.

Resolution

Option 1:
If your VHI solution is not using the Verastream Host Integrator Web Server, you can safely turn this service off. In the properties for this service, set “startup type” to “disabled”. The Verastream Host Integrator Web Server is only used for “HTML5 Web Applications” generated by the Verastream WebBuilder utility, and some older “legacy” types of web applications. It is not used by VHI SOAP or REST web services provided by VHI version 7.0 and later.
Option 2:
To enforce TLS 1.2 as the minimum supported version for the VHI Web Server service:
  • Use VHI version 7.7 with Service Pack 1
  • Edit this file: C:Program FilesAttachmateVerastreamHostIntegratorservletengineconfcontainer.conf
  • Change “wrapper.java.additional.9=-Dmin.supported.tls.protocol=TLSv1” to “wrapper.java.additional.9=-Dmin.supported.tls.protocol=TLSv1.2”
  • Restart the VHI Web Server service.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

  • No Related Posts

7023006: JDBC Connection in Event Handler Code Fails After Installing Service Pack

This document (7023006) is provided subject to the disclaimer at the end of this document.

Environment

Verastream Host Integrator 7.7 Service Pack 1 (7.7.1031)

Situation

After installing Verastream Host Integrator (VHI) 7.7 Service Pack 1, JDBC connections to a Microsoft SQL Server continue to work successfully in VHI event handler code when tested in the VHI Design Tool, but fail when the model is deployed to the VHI server. This exception is seen in error handler console output:

com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: “protocol_version(70)”. ClientConnectionId:33d8d71d-b0e9-4be4-84d8-bd3b237111a0

at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:2670)

at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1837)

at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:2257)

at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:1921)

at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:1762)

at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:1077)

at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:623)

at LcCheckStatus.clientSessionCreated(LcCheckStatus.java:170)

at com.wrq.vhi.script.engine.events.ClientSessionCreatedEventImpl.fireEvent(ClientSessionCreatedEventImpl.java:78)

at com.wrq.vhi.script.engine.SessionProxy.performScriptUpcall(SessionProxy.java:483)

at com.wrq.vhi.script.engine.SessionProxy.runQueuedTasks(SessionProxy.java:133)

at com.wrq.vhi.script.engine.dispatch.SessionWorker.run(SessionWorker.java:130)

Caused by: org.bouncycastle.tls.TlsFatalAlert: protocol_version(70)

at org.bouncycastle.jsse.provider.ProvTlsClient.notifyServerVersion(Unknown Source)

at org.bouncycastle.tls.TlsClientProtocol.receiveServerHelloMessage(Unknown Source)

at org.bouncycastle.tls.TlsClientProtocol.handleHandshakeMessage(Unknown Source)

at org.bouncycastle.tls.TlsProtocol.processHandshakeQueue(Unknown Source)

at org.bouncycastle.tls.TlsProtocol.processRecord(Unknown Source)

at org.bouncycastle.tls.RecordStream.readRecord(Unknown Source)

at org.bouncycastle.tls.TlsProtocol.safeReadRecord(Unknown Source)

at org.bouncycastle.tls.TlsProtocol.blockForHandshake(Unknown Source)

at org.bouncycastle.tls.TlsClientProtocol.connect(Unknown Source)

at org.bouncycastle.jsse.provider.ProvSSLSocketWrap.startHandshake(Unknown Source)

at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1767)

… 10 more

Resolution

Download and install a TLS 1.2 hotfix to update the version of Microsoft SQL Server you are using: https://support.microsoft.com/en-ca/help/3135244/tls-1-2-support-for-microsoft-sql-server

Cause

Older versions of Microsoft SQL Server need to have a hotfix applied in order to be compatible with the new Bouncy Castle security implementation introduced in VHI 7.7 Service Pack 1. TLS 1.2 JDBC connections to SQL Server that were successful using the original VHI 7.7 release will result in the exception noted above for deployed models at the VHI server when Service Pack 1 is applied. Testing in the Design Tool environment, these JDBC event handler connections to SQL Server will continue to succeed because Bouncy Castle security was not implemented for the Design Tool in VHI 7.7 Service Pack 1, only for the VHI server.

On Windows 7 clients and WindowsServer 2008 R2 servers, note additional registry settings are required toenable TLS 1.2 for SQL Server communication. For more information: https://support.microsoft.com/en-ca/help/3135244/tls-1-2-support-for-microsoft-sql-server

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

  • No Related Posts

SSL configuration on VDA

Install SSL server certificates on Controllers

For HTTPS, the XML Service supports SSL features through the use of server certificates, not client certificates. To obtain, install, and register a certificate on a Controller, and to configure a port with the SSL certificate:

Change HTTP or HTTPS ports

By default, the XML Service on the Controller listens on port 80 for HTTP traffic and port 443 for HTTPS traffic. Although you can use non-default ports, be aware of the security risks of exposing a Controller to untrusted networks. Deploying a standalone StoreFront server is preferable to changing the defaults.

To change the default HTTP or HTTPS ports used by the Controller, run the following command from Studio:BrokerService.exe -WIPORT <http-port> -WISSLPORT <https-port>

where <http-port> is the port number for HTTP traffic and <https-port> is the port number for HTTPS traffic.

Note: After changing a port, Studio might display a message about license compatibility and upgrading. To resolve the issue, re-register service instances using the following PowerShell cmdlet sequence:

Get-ConfigRegisteredServiceInstance -ServiceType Broker -Binding XML_HTTPS | Unregister-ConfigRegisteredServiceInstance Get-BrokerServiceInstance | where Binding -eq "XML_HTTPS" | Register-ConfigServiceInstance 


Enforce HTTPS traffic only

If you want the XML Service to ignore HTTP traffic, set the following registry value in HKLMSoftwareCitrixDesktopServer on the Controller and then restart the Broker Service.

To ignore HTTP traffic, set XmlServicesEnableNonSsl to 0.

There is a corresponding registry value to ignore HTTPS traffic: XmlServicesEnableSsl. Ensure that this is not set to 0.

About SSL settings on VDAs

When you configure SSL on VDAs, it changes permissions on the installed SSL certificate, giving the ICA Service read access to the certificate’s private key, and informing the ICA Service of the following:

A Delivery Group cannot have a mixture of some VDAs with SSL configured and some VDAs without SSL configured. When you configure SSL for a Delivery Group, you should have already configured SSL for all of the VDAs in that Delivery Group.

Configure SSL on a VDA using the PowerShell script

The Enable-VdaSSL.ps1 script enables or disables the SSL listener on a VDA. This script is available in the Support >Tools > SslSupport folder on the installation media.

When you enable SSL, the script disables all existing Windows Firewall rules for the specified TCP port before adding a new rule that allows the ICA Service to accept incoming connections only on the SSL TCP port. It also disables the Windows Firewall rules for:

  • Citrix ICA (default: 1494)
  • Citrix CGP (default: 2598)
  • Citrix WebSocket (default: 8008)

The result is that users can connect only over SSL; they cannot use raw ICA, CGP, or WebSocket to connect.

The script contains the following syntax descriptions, plus additional examples; you can use a tool such as Notepad++ to review this information.

You must specify either the –Enable or –Disable parameter; all other parameters are optional.

Syntax

Enable-VdaSSL {-Enable | -Disable} [–SSLPort <port>] [-SSLMinVersion “<min-ssl-version>”] [-SSLCipherSuite“<suite>”] [-CertificateThumbPrint “<thumbprint>”]

Parameter Description
-Enable Installs and enables the SSL listener on the VDA. Either this parameter or the –Disable parameter is required.
-Disable Disables the SSL listener on the VDA. Either this parameter or the –Enable parameter is required. If you specify this parameter, no other parameters are valid.
–SSLPort <port> SSL port. Default: 443
-SSLMinVersion “<min-ssl-version>” Minimum SSL protocol version, enclosed in quotation marks. Valid values: “SSL_3.0”, “TLS_1.0”, “TLS_1.1”, and “TLS_1.2”. Default: “TLS_1.0”
-SSLCipherSuite “<suite>” SSL cipher suite, enclosed in quotation marks. Valid values: “GOV”, “COM”, and “ALL”. Default: “ALL”
-CertificateThumbPrint “<thumbprint>” Thumbprint of the SSL certificate in the certificate store, enclosed in quotation marks. This parameter is generally used when the certificate store has multiple certificates; the script uses the thumbprint to select the certificate you want to use. Default: the first available certificate found in the Local Computer > Personal > Certificates area of the certificate store.

Examples

The following script installs and enables the SSL listener, using default values for all optional parameters.

Enable-VdaSSL –Enable

The following script installs and enables the SSL listener, and specifies SSL port 400, the GOV cipher suite, and a minimum TLS 1.2 SSL protocol value.

Enable-VdaSSL – Enable –SSLPort 400 ‘SSLMinVersion “TLS_1.2” –SSLCipherSuite “GOV”

The following scripts install and enable the SSL Listener on non persistent machine(MCS Catalog) ,thumprint and machine name added of server vda and a minimum TLS 1.2 SSL Protocol value.

Enable-VdaSSL.ps1 -Enable -CertificateThumbPrint (((GEt-ChildItem -Path Cert:LocalMachineMy -DnsName ([System.Net.DNS]::GetHostByName(($env::ComputerName))).Hostname -SSLServerAuthentication) | Where HasPrivateKey -eq 1).Thumbprint) -Confirm:$false -SSLMinVersion TLS_1.2

The following script disables the SSL listener on the VDA.

Enable-VdaSSL –Disable. or Set-ItemProperty -Path "HKLM:SystemCurrentControlSetControlTerminal ServerWdsicawd" -Name "SSLEnabled" -Value 1 -Type DWORD

Manually configure SSL on a VDA

When configuring SSL on a VDA manually, you grant generic read access to the SSL certificate’s private key for the appropriate service on each VDA: NT SERVICEPorticaService for a VDA for Windows Desktop OS, or NT SERVICETermService for a VDA for Windows Server OS. On the machine where the VDA is installed:

  1. Launch the Microsoft Management Console (MMC): Start > Run > mmc.exe.
  2. Add the Certificates snap-in to the MMC:
    1. Select File > Add/Remove Snap-in.
    2. Select Certificates and then click Add.
    3. When prompted with “This snap-in will always manage certificates for:” choose “Computer account”and then click Next.
    4. When prompted with “Select the computer you want this snap-in to manage” choose “Local computer” and then click Finish.
  3. Under Certificates (Local Computer) > Personal > Certificates, right–click the certificate and then select All Tasks > Manage Private Keys.
  4. The Access Control List Editor displays “Permissions for (FriendlyName) private keys” where (FriendlyName) is the name of your SSL certificate. Add one of the following services and give it Read access:
    • For a VDA for Windows Desktop OS, “PORTICASERVICE”
    • For a VDA for Windows Server OS, “TERMSERVICE”
  5. Double-click the installed SSL certificate. In the certificate dialog, select the Details tab and then scroll to the bottom. Click Thumbprint.
  6. Run regedit and go to HKLMSYSTEMCurrentControlSetControlTerminal ServerWdsicawd.
    1. Edit the SSL Thumbprint key and copy the value of the SSL certificate’s thumbprint into this binary value. You can safely ignore unknown items in the Edit Binary Value dialog box (such as ‘0000’ and special characters).
    2. Edit the SSLEnabled key and change the DWORD value to 1. (To disable SSL later, change the DWORD value to 0.)
    3. If you want to change the default settings (optional), use the following in the same registry path:
      • SSLPort DWORD – SSL port number. Default: 443.
      • SSLMinVersion DWORD – 1 = SSL 3.0, 2 = TLS 1.0, 3 = TLS 1.1, 4 = TLS 1.2. Default: 2 (TLS 1.0).
      • SSLCipherSuite DWORD – 1 = GOV, 2 = COM, 3 = ALL. Default: 3 (ALL).
  7. Ensure the SSL TCP port is open in the Windows Firewall if it is not the default 443. (When you create the inbound rule in Windows Firewall, make sure its properties have the “Allow the connection” and “Enabled” entries selected.)
  8. Ensure that no other applications or services (such as IIS) are using the SSL TCP port.
  9. For VDAs for Windows Server OS, restart the machine for the changes to take effect. (You do not need to restart machines containing VDAs for Windows Desktop OS.)

Configure SSL on Delivery Groups

Complete this procedure for each Delivery Group that contains VDAs you have configured for SSL connections.

  1. From Studio, open the PowerShell console.
  2. Run asnp Citrix.* to load the Citrix product cmdlets.
  3. Run Get-BrokerAccessPolicyRule –DesktopGroupName ‘<delivery-group-name>’ | Set-BrokerAccessPolicyRule –HdxSslEnabled $true.

    where <delivery-group-name> is the name of the Delivery Group containing VDAs.

  4. Run Set-BrokerSite –DnsResolutionEnabled $true.

Troubleshooting

If a connection error occurs, check the VDA’s system event log.

When using Receiver for Windows, if you receive a connection error (such as 1030) that indicates an SSL error, disable Desktop Viewer and then try connecting again; although the connection will still fail, an explanation of the underlying SSL issue might be provided (for example, you specified an incorrect template when requesting a certificate from the certificate authority).

Related:

  • No Related Posts

7017147: zypper commands return “SSL certificate problem: unable to get local issuer certificate” on a SLES 12 SUSE Manager Client

The issue is caused by a missing symbolic link on the SLES 12 client. Manually adding the necessary symbolic link should resolve the problem. That can be accomplished by doing the following on the SLES 12 client as root:

1. cd /etc/pki/trust/anchors

2. ls -l

It should look something like this:

total 4

lrwxrwxrwx 1 root root 39 Oct 8 05:19 RHN-ORG-TRUSTED-SSL-CERT.pem -> /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT

If the symbolic link is missing (ie RHN-ORG-TRUSTED-SSL-CERT.pem -> /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT) it can manually be added with:

1. ln -s /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT /etc/pki/trust/anchors/RHN-ORG-TRUSTED-SSL-CERT.pem

2. then run /usr/sbin/update-ca-certificates

zypper commands should once again be working.

Related:

  • No Related Posts

7022944: Replacing an expired apache2 certificate when using mod_nss

1. Back up the original mod_nss.d directory

hostname:~ # cd /etc/apache2

hostname:/etc/apache2 # mv mod_nss.d mod_nss.d-$(date +%y%m%d)

2. Create new mod_nss.d directory

hostname:/etc/apache2 # mkdir mod_nss.d

3. Generate new NSS certificate store in mod_nss.d directory. Do not create a password

hostname:/etc/apache2 # certutil -N -d mod_nss.d

4. Change ownership recursively for that directory to wwwrun user and www group.

hostname:/etc/apache2 # chown -r wwwrun:www mod_nss.d

5. Convert the certificate and key into PKCS12 format

hostname:/etc/apache2 # openssl pkcs12 -export -in /path/to/certificate -inkey /path/to/key -out server.p12 -n “server-cert” -passout pass:<password to encrypt key>

6.

a) Import the PKCS12 certificate

hostname:/etc/apache2 # pk12util -i server.p12 -d mod_nss.d

b) Import the CA chain

hostname:/etc/apache2 # certutil -A -n “ca-chain” -t “CT,,” -d mod_nss.d -a -i /path/to/ca-chain

7. Verify the certificate and CA are imported

hostname:/etc/apache2 # certutil -L -d mod_nss.d

8. Verify the NSSNickName in the existing /etc/apache2/vhosts.d/vhost-nss.conf reflects the Server certificate name in the database. Update as required. This parameter is case-sensitive.

9. Restart apache2 service

hostname:/etc/apache2 # rcapache2 restart

Related:

  • No Related Posts

Vanig International Launches World’s First Integrated E-Commerce and Supply Chain Ecosystem …

Vanig International, (Vanig) is proud to announce the launch of its integrated E-Commerce and Supply Chain Ecosystem.

CHARLESTOWN, St. Kitts and Nevis – May 10, 2018 – (Newswire.com)

E-Commerce is projected to triple by 2030 while today the gross total value of B2B E-Commerce topped $20 trillion in 2017. Vanig is addressing this sizable marketplace with outreach to emerging and established economies.

Key features of Vanig:

Vanig is the world’s first integrated E-Commerce platform and Supply Chain ecosystem powered by the blockchain.

  • Vanig addresses several significant Supply Chain and E-Commerce challenges and inefficiencies, providing a higher level of brand experience.
  • Vanig’s Supply Chain ecosystem leverages the latest in blockchain technology using HyperLedger’s Sawtooth technology.
  • Vanig simplifies the E-Commerce experience and its embedded Supply Chain, eliminating intermediaries, reducing friction and manual processes as it ushers in a new level of transparency.
  • The Vanig platform is safe, secure, and user-friendly, benefiting all members of the ecosystem and allows cryptocurrency payments.
  • Vanig provides provenance information on products, increasingly an essential consumer ask, it is fully integrated in our ecosystem.
  • Vanig uses Artificial Intelligence and Machine Learning to make advertising effective, to certify sellers and provide a customized shopping experience for the buyers.

Vanig was launched successfully in early April with massive participation from the community. Vanig team is now joined by over 20K unique members on Telegram, Twitter and Facebook.

Vanig’s Minimum Viable Product (MVP) is getting closer to release. MVP development integrating Ethereum and Hyperledger Sawtooth, adding self-sovereign identity authentication & verification to the platform is complete.

The Vanig team continues to expand with experts from different fields joining the team. Here are some of the recent additions –

  • David Drake has joined Vanig, founder of LDJ Capital with $1.5 trillion of assets under management. David will assist Vanig with investor outreach, token sale and business development.
  • Paddy Tan and Alan Wong, key advisors to a number of successful ICOs have joined team Vanig. They have a great deal of experience advising companies from planning to funding and execution in Asia.
  • Don Quartiere, a recognized supply chain innovator, most recently engaged at Kuehne + Nagel where he served as a key leader in formulating an inbound logistics strategic plan, will guide Vanig on Supply Chain and Blockchain Technology.
  • Syed Ali and Jeremy Khoo, entrepreneurs, Supply Chain and Retail strategists from South East Asia.

Vanig is also forming exciting partnerships in the South East Asia region. Here are some of our partners so far –

iFashion Group – leading retail venture platform company that owns fashion and lifestyle e-commerce ventures based in Southeast Asia.

MegaxStore – Singapore based marketplace that owns 6 brands and several retail stores, plans to adopt payments in Vanig tokens on its retail stores.

iCommerce Asia – provides a one-stop integrated logistics and supply chain solutions in Southeast Asia.

Dan Ramirez, CEO of Vanig stated:

“We have assembled a global team of experts in E-Commerce, Supply Chain and Blockchain, to work on this ambitious project. We have also forged great partnerships with exciting companies in the South East Asia region to enable us to make quick progress with our rollout once we finish our Token Sale. We are in private sale period now and our main token sale will be live from June 2018. The journey is just getting started for Vanig and team Vanig is all geared up for this challenging and exciting ride.”

Visit the Website:https://www.vanig.io

Meet the Team:https://www.vanig.io/#team

Read the Whitepaper:https://vanig.io/assets/pdfs/vanig-whitepaper-v-4.2.pdf

Get in touch on Telegram:https://t.me/vanigplatform

Media Contact

Name: Prem Sekaran

Contact Email:prem@vanig.io

Vanig is the source of this content. Virtual currency is not legal tender, is not backed by the government, and accounts and value balances are not subject to consumer protections. Cryptocurrencies and tokens are extremely volatile. There is no guarantee of a stable value, or of any value at all. Token sales are only suitable for individuals with a high-risk tolerance. Only participate in a token event with what you can afford to lose. This press release is for informational purposes only. The information does not constitute investment advice or an offer to invest.

Related Links

Vanig

Bitcoin PR Buzz

Press Release Service by Newswire.com

Original Source: Vanig International Launches World’s First Integrated E-Commerce and Supply Chain Ecosystem Powered by Blockchain

Related:

  • No Related Posts