Bug: [DOCUMENTATION] Updating the readme for dashboard visibility



### Feature Description

Sandbox dashboard is one step away for new users landing on Github page. 
Hence increasing the visibility of app.hyperswitch.io

### Possible Implementation

Sandbox dashboard is one step away for new users landing on Github page. 
Hence increasing the visibility of app.hyperswitch.io

### Have you spent some time to check if this feature request has been raised before?

- [X] I checked and didn't find similar issue

### Have you read the Contributing Guidelines?

- [X] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)

### Are you willing to submit a PR?

Yes I am willing to submit a PR!
diff --git a/README.md b/README.md
index c477ed15aa9..89f6e94f4df 100644
--- a/README.md
+++ b/README.md
@@ -52,21 +52,24 @@ Using HyperSwitch, you can:
 
 ## Quick Start Guide
 
-You have three options to try out HyperSwitch:
 
-1. [Try it in our Sandbox Environment](/docs/try_sandbox.md): Fast and easy to
+<a href="https://app.hyperswitch.io"><img src="./docs/imgs/signup-to-hs.svg" height="35"></a>
+
+Ways to get started with Hyperswitch:
+
+1. Try it in our Sandbox Environment: Fast and easy to
    start.
-   No code or setup required in your system.
-2. Try our React Demo App: A simple demo of integrating Hyperswitch with your
-   React app.
+   No code or setup required in your system, [learn more](/docs/try_sandbox.md)
+
+
+<a href="https://app.hyperswitch.io"><img src="./docs/imgs/get-api-keys.svg" height="35"></a>
+
+2. A simple demo of integrating Hyperswitch with your React App, Try our React [Demo App](https://github.com/aashu331998/hyperswitch-react-demo-app/archive/refs/heads/main.zip).
 
-   <a href="https://github.com/aashu331998/hyperswitch-react-demo-app/archive/refs/heads/main.zip">
-   <img src= "./docs/imgs/download-button.png" alt="Download Now" width="190rem" />
-   </a>
 
-3. [Install in your local system](/docs/try_local_system.md): Configurations and
+3. Install in your local system: Configurations and
    setup required in your system.
-   Suitable if you like to customize the core offering.
+   Suitable if you like to customize the core offering, [setup guide](/docs/try_local_system.md)
 
 ## Fast Integration for Stripe Users
 
@@ -85,7 +88,7 @@ Try the steps below to get a feel for how quick the setup is:
 
 ### Supported Payment Processors and Methods
 
-As of Jan 2023, we support 14 payment processors and multiple payment methods.
+As of Apr 2023, we support 30 payment processors and multiple payment methods.
 In addition, we are continuously integrating new processors based on their reach
 and community requests.
 Our target is to support 100+ processors by H2 2023.

## Type of Change
<!-- Put an `x` in the boxes that apply -->

- [ ] Bugfix
- [ ] New feature
- [x] Enhancement
- [ ] Refactoring
- [ ] Dependency updates

## Description
Adding a button linking to dashboard
<!-- Describe your changes in detail -->


### Additional Changes

- [ ] This PR modifies the database schema
- [ ] This PR modifies application configuration/environment variables

<!-- 
Provide links to the files with corresponding changes.

Following are the paths where you can find config files:
1. `config`
2. `crates/router/src/configs`
3. `loadtest/config`
-->


## Motivation and Context

Suggested by @NarsGNA 
<!--
Why is this change required? What problem does it solve?
If it fixes an open issue, please link to the issue here.

If you don't have an issue, we'd recommend starting with one first so the PR
can focus on the implementation (unless its an obvious bug or documentation fix
that will have little conversation).
-->


## How did you test it?
<!--
Did you write an integration/unit/API test to verify the code changes?
Or did you test this change manually (provide relevant screenshots)?
-->


## Checklist
<!-- Put an `x` in the boxes that apply -->

- [x] I formatted the code `cargo +nightly fmt --all`
- [x] I addressed lints thrown by `cargo clippy`
- [x] I reviewed submitted code
- [ ] I added unit tests for my changes where possible
- [ ] I added a [CHANGELOG](/CHANGELOG.md) entry if applicable
