Wise

Website

wise.com

$ Details

-

Categories

#Online Payments #Money Transfer #International Money Transfers #Currency Exchange

Startup details

Country

United Kingdom

GraphQL

Website

graphql.org

$ Details

Categories

#Developer Tools #JavaScript Framework #Web Frameworks #Javascript UI Libraries

Wise features and specs

• Low Fees
  Wise offers competitive and transparent fees compared to traditional banks and many other money transfer services.
• Real Exchange Rates
  Wise uses the mid-market exchange rate, meaning users get the real exchange rate without any hidden markups.
• Fast Transfers
  Many transfers through Wise are processed quickly, often within a few hours or a day, depending on the destination country and payment method.
• Multi-Currency Accounts
  Users can hold and manage money in multiple currencies with Wise's Borderless Account, making it easier for those who deal with international payments regularly.
• Transparent Pricing
  Wise is upfront about their fees and the total cost of a transfer, so users know exactly how much they'll pay and how much the recipient will receive.
• User-Friendly Interface
  Wise offers a clean and intuitive application and web interface, making it easy for users to navigate and complete transactions.

Possible disadvantages of Wise

• Limited Customer Support
  Wise's customer support is primarily online, and some users report difficulties in reaching live assistance or having slow response times.
• Transfer Limits
  There are limits on how much money can be transferred in a single transaction or over a period of time, which might be restrictive for some users.
• Lack of Physical Locations
  Unlike traditional banks, Wise doesn't have physical branches, which can be an inconvenience for those who prefer in-person banking services.
• Verification Process
  New users or those making large transfers may have to go through a lengthy verification process, which can delay the initial transaction.
• Not Available in All Countries
  Wise does not operate in every country, limiting its accessibility for some users looking to send or receive international payments.
• Occasional Delays
  While generally fast, some transfers may experience delays due to various factors, such as banking hours, holiday schedules, or compliance checks.

GraphQL features and specs

• Efficient Data Retrieval
  GraphQL allows clients to request only the data they need, reducing the amount of data transferred over the network and improving performance.
• Strongly Typed Schema
  GraphQL uses a strongly typed schema to define the capabilities of an API, providing clear and explicit API contracts and enabling better tooling support.
• Single Endpoint
  GraphQL operates through a single endpoint, unlike REST APIs which require multiple endpoints. This simplifies the server architecture and makes it easier to manage.
• Introspection
  GraphQL allows clients to query the schema for details about the available types and operations, which facilitates the development of powerful developer tools and IDE integrations.
• Declarative Data Fetching
  Clients can specify the shape of the response data declaratively, which enhances flexibility and ensures that the client and server logic are decoupled.
• Versionless
  Because clients specify exactly what data they need, there is no need to create different versions of an API when making changes. This helps in maintaining backward compatibility.
• Increased Responsiveness
  GraphQL can batch multiple requests into a single query, reducing the latency and improving the responsiveness of applications.

Possible disadvantages of GraphQL

• Complexity
  The setup and maintenance of a GraphQL server can be complex. Developers need to define the schema precisely and handle resolvers, which can be more complicated than designing REST endpoints.
• Over-fetching Risk
  Though designed to mitigate over-fetching, poorly designed GraphQL queries can lead to the server needing to fetch more data than necessary, causing performance issues.
• Caching Challenges
  Caching in GraphQL is more challenging than in REST, since different queries can change the shape and size of the response data, making traditional caching mechanisms less effective.
• Learning Curve
  GraphQL has a steeper learning curve compared to RESTful APIs because it introduces new concepts such as schemas, types, and resolvers which developers need to understand thoroughly.
• Complex Rate Limiting
  Implementing rate limiting is more complex with GraphQL than with REST. Since a single query can potentially request a large amount of data, simple per-endpoint rate limiting strategies are not effective.
• Security Risks
  GraphQL's flexibility can introduce security risks. For example, improperly managed schemas could expose sensitive information, and complex queries can lead to denial-of-service attacks.
• Overhead on Small Applications
  For smaller applications with simpler use cases, the overhead introduced by setting up and maintaining a GraphQL server may not be justified compared to a straightforward REST API.

Analysis of Wise

TransferWise Review - 3 Must Knows (2020)

More videos:

REST vs. GraphQL: Critical Look

More videos: