Home

Globalization has revolutionized business environment with the increasing amount of businesses and individuals making use of overseas suppliers. This trend is increasing the demand for transactions across borders. The rise in international commerce, ecommerce and internationalization of production shows that the demand for cross-border payments is expected to continue to increase rapidly. A Forrester study forecasts that cross-border eCommerce would span over at least 29 countries in Europe, Asia Pacific, Africa, North America, Latin America, and the Middle East by the year 2022.

The process of sending money from one place to another, be it to relatives, friends or even to pay for goods or services it is more expensive, time-consuming difficult, inconvenient as well as less transparent than regular domestic payments. This could have to do with the complexity involved in payments across borders with more risk and regulations than regular domestic payments.

In order to address these problems blockchain technology is a single-stop solution for improving the overall effectiveness of cross-border payment. A cross-border payment system built on the blockchain platform Stellar will make sure that financial services are accessible to people who have limited or no banking services. These include interconnections with domestic payment systems, expansion of closed-loop systems that are proprietary to boundaries, and peer-to-peer payments systems that are based on blockchain.

What are the problems facing traditional cross-border payment system?

The term “cross-border payment” refers to the process that see the money transferred from one nation and then to a different country. The traditional cross-border transaction consists of several entities such as banks and financial institutions, schemes providers, or even individuals who want to transfer funds across different territories.

When the funds are deposited the funds are processed and transferred through fragmented financial institutions. Each time, the fund’s custody shifts and the institution is charged fees in the range of a certain percentage. This results in increasing costs for the person who is sending. The total charges are calculated based on the amount of transfer as well as the country of destination. The whole process isn’t all that expensive, but it is also lengthy. Because the sender and the receiver do not have a shared ledger, the transaction has to be executed through a number of intermediaries. Payments across borders are essential when purchasing goods and services from one country to the next. But, they aren’t the most convenient option due to:

• The processing of international payments through banks is complex and difficult.
• Unpredictable currency exchange rates.
• The risk of robbery, hacking or theft.

1. Older operational systems

Banks typically encounter the problem of the messaging infrastructure when it comes to cross-border transactions. The majority of payments across borders are made using the SWIFT the MT103 messaging format. It is a reliable format, but can’t carry a lot of information over the limit of. If you require additional information, it’s handled via email. The manual process and non-automated messages in both the transactions render this process inefficient.

2. Inefficient payment processing

Because of a lengthy and complex process that cross-border payments can stop at any time. This can lead to delays and a negative client satisfaction for all parties. The reason for this delay could be the inadequacy of data on the payment as well as the need to conduct sanction checks or AML checks or fraud. Because of the absence of digitization in the data sharing process, transactions have to pass through several sophisticated communication channels.

For instance the transfer of funds between banks internationally is the traditional method to make international payments. Many of the major banks are able to hold a restricted amount of currency. If a sender from the US wants for a transfer of funds into UK. UK however the banking institutions don’t hold enough currency stocks. In these situations they will have to rely on their foreign bank partners for the execution of the transactions. Because the smaller banks don’t have foreign currency, they choose to use large banks to handle the cross-border transactions for them. This is just one situation, however there are many intermediaries involved in these procedures, which can cause delays in transactions.

The majority of B2B international payments are processed by banks. The transaction needs to pass through intermediary institutions such as banks, central banks overseas banks, and the central bank. Each has an accounting system that is independent. This means that the bank accounts require clearing and reconciliation with the other counterparties in a single transaction. This is a slow process which results in the need to take longer processing the transactions.

3. Privacy rules

A majority of banks must adhere to the regulations regarding privacy of personal data. The regulations define which customer’s information needs to be shared across various regions for processing the transaction. The separation, sorting, and arranging of this data takes a considerable amount of time. For instance, in some countries, banks are not able to communicate information about their clients between various departments. This regulation can be implemented with the help of a technological solution to make it easier for the whole procedure.

4. Lack of Security, Transparency and Low Security

Regular cross-border payment uses centralized payment. Customers are required to share their account as well as other details with intermediaries. Based on this information intermediaries process remittances as well as withdrawals. These massive customer data as well as transaction information shared that are shared with intermediaries could be an easy attack for hackers. When using third-party services for transactions that cross borders the transaction information is available across various platforms, foreign merchants and banks. This means that the data is more susceptible to being released in these modes. The parties involved with the transactions can’t keep track of their payments. As a result it is difficult to determine the final amount of payment as well as the time of delivery date.

5. Expensive

Fees are accrued through the bank that sends the money to international and national correspondent banks as well as foreign exchange exchanges at each stage through the process. The cost is typically at least 3 percent for high volume international payments. However, it could increase to 10% if the volume and value of payments aren’t high enough. It is also not clear whether institutions that make payments charge fees to the recipient.

For instance credit cards are a the most popular choice for customers who want to make cross-border transactions. All they have to do is input their card information and wait for their card to be authenticated. It’s a simple process but there’s more that is happening in the background. The cross-border payments require more effort from the credit card networks as well as the involved banks to convert the two currencies. The added workload results in an cost of the transaction which is passed along through the chain of payment.

Read More : https://www.leewayhertz.com/cross-border-payments-on-stellar/

Stellar is a decentralized , open network for sharing and storing funds. Jed McCaleb, the founder of Stellar created Stellar with the intention of providing users with the ability to transfer their fiat currency with digital currency easily.

Developers who create applications on base of Stellar network software making use of Stellar SDKs that they use in their programming languages of choice. SDKs then communicate with Horizon Stellar-network API. Horizon offers a means to verify accounts, join to events, and send transactions.

Stellar ecosystem is based on an API server dubbed Horizon. It functions in the role of an interfacing with Stellar Core and the applications that are part of the Stellar network. It also offers HTTP API for data on data on the Stellar network. It obtains information from data in the Stellar network and serves the data in a format that is simple to access.

There are various benefits for running Horizon with your infrastructure:

• Control the entire operation without any dependence upon any of Stellar Development Foundation
• Set up multiple instances to handle capacity and redundancy
• Enable rate-limiting of requests to ensure access to the network

Prerequisites

Horizon is dependent in the PostgreSQL server to store the data that is processed and ingested by Stellar Core. The PostgreSQL Version 9.5 or greater is required to run Horizon.

The additional RAM required is to host Captive Core’s memory database, which would amount to around 3GB. The second requirement is based on the volume of history of the network that is served by your Horizon instance. It can range from a few GBs up to hundreds of TBs to cover the entire history of ledgers ingested.

Installation

First, prebuilt binaries downloaded from Stellar repositories must be installed prior to installing Horizon. If you’re not keen to install prebuilt releases you can choose another method. It is necessary to build Horizon from source. Some developer tools will must be installed for this purpose:

• OS that is similar to Unix that uses common basic commands such as mkdir, bash, cp, and so on.
• Go1.15 or later
• Git

Configuration

Parameters

Both command line flags and environmental variables can affect Horizon’s configuration. Use the following command to look up the available command-line flags along with their default values as well as the associated environmental variables:

Horizon -help

The command above will show many flags, but only a few are needed. The three most significant parameters are:

• -db_url: It is the name of the Horizon database. Its value must be an authentic PostgreSQL link URL.

• -captive-core-config-append-path: It points to a Captive Core configuration stub.

• -stellar-core-binary-path: It is a file system path to a Stellar Core binary. Horizon scans PATH to find stellar-core automatically; however, if the environment is properly configured then there is no need to specify the path manually.

Read More: https://www.leewayhertz.com/run-stellar-api-server/

Stellar is one of the most fast-paced payments that are low-cost technology that is open-sourced by the sense that it is open-sourced in. Stellar technology is also comparable to Ripple in terms of ripple in the sense of specific characteristics of transactions, and also interestingly one of the founders of Ripple, Jed McCaleb, is also the creator of Stellar.

Stellar is described as a platform that facilitates banks to connect, as well as the payment system, and for the general public. It was designed to facilitate the flow of money and transactions swiftly and efficiently, while enjoying the benefits of trust as well as the lowest cost.

What do you understand by a Stellar Horizon Server? 

Horizon can be described as an API server to the entire ecosystem of Stellar. Horizon acts as an interface between applications that want to connect to the Stellar network as well as stellar-core. Horizon allows you to send payments for Stellar network, transfer transactions to the Stellar network, monitor the status of accounts and assists with event stream subscriptions as well as other. Horizon is responsible as a provider of an HTTP API to data from the Stellar network. Horizon ingests and stores the data created from Stellar Core and the Stellar network, in a way that is more easily consumed by any application compared to the performance-oriented representations of data that are used in Stellar Core. There is no need to create the own Horizon instance to connect to the Stellar network. There is two Horizon servers operated by the Stellar development foundation, specifically public and test networks:

• https://horizon-testnet.stellar.org./

• https://horizon.stellar.org/

They are free servers accessible to anyone and are ideal to develop projects and research at a smaller scale. However, their use is low and they’re not recommended in the case of production services which require confidence and security.

Read More: https://www.leewayhertz.com/set-up-stellar-horizon-aws/

Presently, stellar is among the most popular blockchain platforms around the world. It permits its users to create assets, and then connect these to bank railways or networks to transfer value into the network, and off it. These connections are made by services called “Anchors”. The majority of anchors create the infrastructure for Stellar by following the best practices outlined in SEPs. These guidelines allow wallets that allow deposit and withdrawals in app.

Stellar Ecosystem Proposals (SEPs) are open-source documents which are designed to define the manner in which interoperation and interactions must occur between various institutions like exchanges, asset issuers wallets and even service suppliers. SEP-24 will be the document that specifies the guidelines for withdrawals and deposits. It allows withdrawal and deposit of cryptocurrencies such as ETH, BTC and ERC20 tokens such as USDT. SEP-24 is also dependent on SEP-1 (links meta-information about organizations as well as assets) as well as SEP-10 (creates an authenticated users sessions).

The wallet and anchor applications is necessary to allow withdrawals and deposits of an asset either on or off Stellar. Therefore, in this article, we’ll examine the essential steps to create a server SEP-24 to allow users to make deposits and withdraws on Stellar.

How can I setup withdrawals and deposits via Stellar?

David is a client who wishes to make a deposit on the excellent network. This is how the process will go:

• David will launch the wallet application SEP-24 that he prefers using his mobile device.

• When he has selected an account to fund, the wallet will locate an anchor or David can select a particular anchor.

• After the wallet is authenticated by the anchor, it will input the KYC and transaction details as the anchor asks.

• The wallet will offer instructions. Upon following these, the user will be able to deposit fiat currencies using an anchor (e.g. it is possible to perform a transfer to a bank).

• When the wallet has received his payment, it will be able to be able to receive the tokenized asset through the distribution account of the anchor through the Stellar network.

David can utilize the digital currency on the Stellar network for various use instances such as transactions, payments, remittances stores of value, etc.

If, in the future David would like to remove his funds away from the Stellar network This is the way he’ll do it:

1. Open the wallet application, choose the account to withdraw and then his wallet will locate the anchor.
2. Once it has authenticated with the anchor it will then be able to open the interactive URL and permit David to input his details for transactions (KYC was already completed)
3. The wallet will seek his consent before sending the amount specified of his balance in assets to the distribution account of the anchor on Stellar
4. When the anchor has received the money, David will receive the money through a bank transfer.

Tools and References

For handling withdrawals and deposits You will need to create and run the test server as well as the production server. While we’ll go over all the steps required in this post but you should also consider that the SDF has tools that help you set up the servers and allows testing via the client-side. This means that you don’t have to begin with a blank slate:

• Anchor Server Reference implementation: Polaris is an extensible Django application that is reusable and developed with the help of SDF using Python to make modular the components of the codebase which interface with the fantastic network. They offer clear ways to integrate your withdrawal and deposit forms, KYC process and banking rail connections.

• Demo Client and Deployed Example: SDF maintains an Demo Wallet Project to simplify testing your application for both pubnet and testnet. It is possible to run these tests by using a UI, without establishing a new hosting infrastructure. You will also get an encapsulated visual representation of how these functions function step-by-step, with other useful details.

• Anchor Validation Suite: It is a series of tests designed to verify that your anchor’s configuration is compatible with the most current SEP-24 standards or is not.

Read More: https://www.leewayhertz.com/set-up-deposits-withdrawals-stellar/

Stellar has the ability to issue assets as one of its core features. Stellar makes it easy to tokenize assets and trade them over the Stellar network. It’s easy to do, it’s quick and economically possible, and anyone can do it (banks, money service businesses and payment processors, local communities and enterprises, as well as individuals). Stellar offers a number of options to help you tune your assets for specific purposes. These assets can be listed on the Stellar decentralized market and used by market-making robots to take advantage of Stellar’s global reach to ensure that they have the liquidity required. Stellar is currently focusing on the tokenization and optimization of cross-border payments processes.

Anatomy and Function of an Asset

These are the two hallmarks of any Stellar asset

The Asset Code

Two supported formats are available for the asset code: the alphanumeric 4-character maximum, and the alphanumeric 12 character maximum. It is an identifying number that allows token holders to identify what your token is.

The Issuer

A payment operation creates assets on stellar. The account issuing the asset is called the issuer. The network asset is created by the payment made to the issuing account. The asset’s control and management are the responsibility of the issuing bank.

These characteristics allow Stellar to identify the asset for interaction. Sometimes asset codes overlap, as multiple organizations can issue credit representing the same asset. Each asset can be uniquely identified by the combination of the issuer code and the asset number. These stellar tokens allow you to redeem anything outside of the network. This includes bonds, fiat currency and carbon credits. When issuing currency, it should have the correct ISO 4217 code. If issuing stock or bonds, it should have the appropriate ISIN number.

Trustlines

With a change_trust operation, trustlines are account-level entries that persist. Each account must create a trustline in order to hold assets issued by other accounts. It identifies both the issuer as well as the asset code. There are some functions that trustlines can perform:

• An account’s minimum lumen amount should be increased by one base reserve (currently, 0.5XLM), and the asset’s balance should also be tracked.

• Limit the amount of an asset that is held in an account.

• Monitor liabilities.

Trustlines should have enough cash to meet its selling obligations and enough money to pay its buying obligations.

Amount Precision

Asset amounts can be encoded in XDR structures using signed 64-bit integers. These structures are used to encode transactions by Stellar. To get to the native 64-integer representation, end-users scale down the asset unit by a factor ten million.

Int64s is used to represent numbers. To prevent bugs from arising from mixing signed and unsigned numbers, the amount values are stored only in signed integers.

Read More: https://www.leewayhertz.com/issue-assets-on-stellar-blockchain/