Skip to content

Commit 9d5fa36

Browse files
aditya-67aditya-67
committed
UMAP -> UPI Setu
1 parent 3497a13 commit 9d5fa36

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

66 files changed

+2319
-2006
lines changed

‎content/endpoints.json

+1-1
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@
4444
"visible_in_sidebar": false
4545
},
4646
{
47-
"name": "UMAP",
47+
"name": "UPI Setu",
4848
"path": "umap",
4949
"order": 7,
5050
"visible_in_sidebar": true

‎content/menuItems.json

+1-1
Large diffs are not rendered by default.

‎content/payments/umap/api-integration.mdx

+83-84
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
22
sidebar_title: API integration
3-
page_title: UMAP - API integration
3+
page_title: UPI Setu - API integration
44
order: 2
55
visible_in_sidebar: true
66
---
77

88
## API integration guide
99

10-
A `clientID` and `secret` together is called an **API key**. An **API key** can be used to access resources on one deployment environment specifically, either `Test` or `Live`, but not both. Once you get the `clientID` and `secret` from Setu, use them to generate tokens to authorise all API requests.
10+
A `clientID` and `secret` together is called an **API key**. An **API key** can be used to access resources on one deployment environment specifically, either `Test` or `Live`, but not both. Once you get the `clientID` and `secret` from Setu, use them to generate tokens to authorise all API requests.
1111

1212
<hr class="primary" />
1313

@@ -18,120 +18,119 @@ An API to generate access tokens, which are used to authorise any other API requ
1818
**Request**
1919

2020
<table>
21-
<tr>
22-
<th>Host</th>
23-
<td>
24-
<code>https://accountservice.setu.co</code>
25-
</td>
26-
</tr>
27-
<tr>
28-
<th>Method</th>
29-
<td>
30-
<code>POST</code>
31-
</td>
32-
</tr>
33-
<tr>
34-
<th>Path</th>
35-
<td>
36-
<code>/v1/users/login</code>
37-
</td>
38-
</tr>
39-
<tr>
40-
<th>Header</th>
41-
<td>
42-
<code>client</code>— will be <code>bridge</code>
43-
<br />
44-
<code>Content-Type</code>— will be <code>application/json</code>
45-
</td>
46-
</tr>
21+
<tr>
22+
<th>Host</th>
23+
<td>
24+
<code>https://accountservice.setu.co</code>
25+
</td>
26+
</tr>
27+
<tr>
28+
<th>Method</th>
29+
<td>
30+
<code>POST</code>
31+
</td>
32+
</tr>
33+
<tr>
34+
<th>Path</th>
35+
<td>
36+
<code>/v1/users/login</code>
37+
</td>
38+
</tr>
39+
<tr>
40+
<th>Header</th>
41+
<td>
42+
<code>client</code>— will be <code>bridge</code>
43+
<br />
44+
<code>Content-Type</code>— will be <code>application/json</code>
45+
</td>
46+
</tr>
4747
</table>
4848

4949
<br />
5050

51-
5251
<Tabs
53-
tabs={[
54-
{
55-
key: "1",
56-
label: "Request body",
57-
content: (
58-
<>
59-
<CodeBlockWithCopy language="json">
60-
{`{
52+
tabs={[
53+
{
54+
key: "1",
55+
label: "Request body",
56+
content: (
57+
<>
58+
<CodeBlockWithCopy language="json">
59+
{`{
6160
"clientID": "client_id",
6261
"secret": "client_secret",
6362
"grant_type": "client_credentials"
6463
}`}
65-
</CodeBlockWithCopy>
66-
</>
67-
),
68-
},
69-
{
70-
key: "2",
71-
label: "Response body",
72-
content: (
73-
<>
74-
<CodeBlockWithCopy language="json">
75-
{`{
64+
</CodeBlockWithCopy>
65+
</>
66+
),
67+
},
68+
{
69+
key: "2",
70+
label: "Response body",
71+
content: (
72+
<>
73+
<CodeBlockWithCopy language="json">
74+
{`{
7675
"access_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhY2Nlc3NfdG9rZW4iOiJhY2Nlc3NfdG9rZW4iLCJyZWZyZXNoX3Rva2VuIjoic3RyaW5nIn0.HfoWXjOPViPG0BWnZ7ZGahD9UXacsjl9vrYXVIHOcW8"
7776
}`}
78-
</CodeBlockWithCopy>
79-
</>
80-
),
81-
},
82-
{
83-
key: "3",
84-
label: "cURL request",
85-
content: (
86-
<>
87-
<CodeBlockWithCopy language="bash">
88-
{`curl --location 'https://accountservice.setu.co/v1/users/login' \
77+
</CodeBlockWithCopy>
78+
</>
79+
),
80+
},
81+
{
82+
key: "3",
83+
label: "cURL request",
84+
content: (
85+
<>
86+
<CodeBlockWithCopy language="bash">
87+
{`curl --location 'https://accountservice.setu.co/v1/users/login' \
8988
--header 'client: bridge' \
9089
--header 'Content-Type: application/json' \
9190
--data '{
9291
"clientID": "client_id",
9392
"secret": "client_secret",
9493
"grant_type": "client_credentials"
9594
}'`}
96-
</CodeBlockWithCopy>
97-
</>
98-
),
99-
}
100-
]}
95+
</CodeBlockWithCopy>
96+
</>
97+
),
98+
},
99+
]}
101100
/>
102101

103102
<Callout type="tip">
104-
💡 The <code>access_token</code> is valid for <code>300s</code>. The <code>access_token</code> can be <code>reused</code> any number of times within its expiry, so it is advised to cache the token.
103+
💡 The <code>access_token</code> is valid for <code>300s</code>. The{" "}
104+
<code>access_token</code> can be <code>reused</code> any number of times
105+
within its expiry, so it is advised to cache the token.
105106
</Callout>
106107

107-
<br/>
108+
<br />
108109

109110
###### How to use the access token
110111

111-
- Once you have a valid token, you can use it to authorise an API calls made to Setu, by setting the `Authorization` request header as `Bearer <access_token>`.
112-
- To get the new token, call the same `login` API at the 4th minute of token expiry and get the new token for the further API calls.
112+
- Once you have a valid token, you can use it to authorise an API calls made to Setu, by setting the `Authorization` request header as `Bearer <access_token>`.
113+
- To get the new token, call the same `login` API at the 4th minute of token expiry and get the new token for the further API calls.
113114

114115
<hr class="primary" />
115116

116117
#### Proceed with integration
117118

118119
<Row>
119-
<Portion desktopSpan="half">
120-
<Card padding="small" shape="rounded">
121-
<Link href="/payments/umap/api-integration/merchants">
122-
Merchants
123-
</Link>
124-
<p>Integrate as a merchant to start accepting payments over UPI.</p>
125-
</Card>
126-
</Portion>
127-
<Portion desktopSpan="half">
128-
<Card padding="small" shape="rounded">
129-
<Link href="/payments/umap/api-integration/aggregators">
130-
Aggregators
131-
</Link>
132-
<p>Integrate as an aggregator, to on-board and manage multiple merchants.</p>
133-
</Card>
134-
</Portion>
120+
<Portion desktopSpan="half">
121+
<Card padding="small" shape="rounded">
122+
<Link href="/payments/umap/api-integration/merchants">Merchants</Link>
123+
<p>Integrate as a merchant to start accepting payments over UPI.</p>
124+
</Card>
125+
</Portion>
126+
<Portion desktopSpan="half">
127+
<Card padding="small" shape="rounded">
128+
<Link href="/payments/umap/api-integration/aggregators">Aggregators</Link>
129+
<p>
130+
Integrate as an aggregator, to on-board and manage multiple merchants.
131+
</p>
132+
</Card>
133+
</Portion>
135134
</Row>
136135

137136
<WasPageHelpful />

‎content/payments/umap/api-integration/aggregators.mdx

+4-4
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
sidebar_title: Aggregators
3-
page_title: UMAP - API integration for aggregators
3+
page_title: UPI Setu - API integration for aggregators
44
order: 1
55
visible_in_sidebar: true
66
---
@@ -16,18 +16,18 @@ visible_in_sidebar: true
1616

1717
<hr class="primary" />
1818

19-
Once you have been on-boarded on to Bridge as an aggregator and business formalities have been completed, you can proceed to integrate UMAP APIs with your internal systems. First, you have to create a merchant and then enable products that the merchant can use.
19+
Once you have been on-boarded on to Bridge as an aggregator and business formalities have been completed, you can proceed to integrate UPI Setu APIs with your internal systems. First, you have to create a merchant and then enable products that the merchant can use.
2020

2121
<hr class="primary" />
2222

2323
#### Step 1 — Configure a merchant
2424

25-
As an aggregator on UMAP, you have to first create a merchant by providing their business details and creating a VPA (which associates them to you, the aggregator). After this, you can enable UPI products for the merchant.
25+
As an aggregator on UPI Setu, you have to first create a merchant by providing their business details and creating a VPA (which associates them to you, the aggregator). After this, you can enable UPI products for the merchant.
2626

2727
<Card padding="small" shape="rounded">
2828
<Link href="/payments/umap/merchant-onboarding">Merchant on-boarding</Link>
2929
<Text weight="400" marginTop="nano" marginBottom="none" size="small">
30-
Create your first merchant on UMAP
30+
Create your first merchant on UPI Setu
3131
</Text>
3232
</Card>
3333

‎content/payments/umap/api-integration/merchants.mdx

+3-3
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
sidebar_title: Merchants
3-
page_title: UMAP - API integration for merchants
3+
page_title: UPI Setu - API integration for merchants
44
order: 2
55
visible_in_sidebar: true
66
---
@@ -16,9 +16,9 @@ visible_in_sidebar: true
1616

1717
<hr class="primary" />
1818

19-
#### What can you do with UMAP?
19+
#### What can you do with UPI Setu?
2020

21-
Once you have on-boarded onto UMAP as a merchant, and have your API credentials, the next step is to choose the right product for your use case. Below are some example scenarios to help you understand these products better—
21+
Once you have on-boarded onto UPI Setu as a merchant, and have your API credentials, the next step is to choose the right product for your use case. Below are some example scenarios to help you understand these products better—
2222

2323
<table>
2424
<tr>

‎content/payments/umap/api-reference.mdx

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
sidebar_title: API reference
3-
page_title: UMAP - API reference
3+
page_title: UPI Setu - API reference
44
order: 8
55
visible_in_sidebar: true
66
---

‎content/payments/umap/mandates.mdx

+38-17
Original file line numberDiff line numberDiff line change
@@ -7,35 +7,56 @@ visible_in_sidebar: true
77

88
# UPI mandates
99

10-
UPI mandates is a recurring payments product built on the same rails of UPI which enables businesses to create subscriptions or one-time block based payments seamlessly via the user's favourite UPI app.
10+
UPI mandates is a recurring payments product built on the same rails of UPI which enables businesses to create subscriptions or one-time block based payments seamlessly via the user's favourite UPI app.
1111

1212
### What can you do with UPI mandates?
13-
Choose one or more of our products under the UMAP mandates stack to—
14-
* Enable limited stock purchases like IPO investments on your wealth app
15-
* Create seamless subcsriptions for your services directly from UPI apps
16-
* Reimagine **cash on delivery** or **try and buy** with single block multi debits
13+
14+
Choose one or more of our products under the UPI Setu mandates stack to—
15+
16+
- Enable limited stock purchases like IPO investments on your wealth app
17+
- Create seamless subcsriptions for your services directly from UPI apps
18+
- Reimagine **cash on delivery** or **try and buy** with single block multi debits
1719

1820
###### Explore our mandate products
19-
<UMAPMandates />
21+
22+
<UPI SetuMandates />
2023

2124
### Key features
2225

2326
<img
24-
src="https://storage.googleapis.com/strapi-assets/latest/Frame_106/Frame_106.png"
25-
alt="Bridge"
27+
src="https://storage.googleapis.com/strapi-assets/latest/Frame_106/Frame_106.png"
28+
alt="Bridge"
2629
/>
2730

2831
#### UPI mandate statuses
2932

3033
A mandate can have any of the below statuses throughout its life-cycle—
3134

3235
<Text>
33-
<ul>
34-
<li><code>mandate.initiated</code>&nbsp;A mandate creation request has been initiated</li>
35-
<li><code>mandate.live</code>&nbsp;Customer authorisation received & mandate is now active</li>
36-
<li><code>mandate.rejected</code>&nbsp;Due to error or no authorisation, mandate could not be created</li>
37-
<li><code>mandate.paused</code>&nbsp;Customer has decided to temporarily stop executions on mandate</li>
38-
<li><code>mandate.revoked</code>&nbsp;Mandate was closed by customer or merchant before expiry</li>
39-
<li><code>mandate.complete</code>&nbsp;Mandate executions are done, and now mandate is closed</li>
40-
</ul>
41-
</Text>
36+
<ul>
37+
<li>
38+
<code>mandate.initiated</code>&nbsp;A mandate creation request has been
39+
initiated
40+
</li>
41+
<li>
42+
<code>mandate.live</code>&nbsp;Customer authorisation received & mandate
43+
is now active
44+
</li>
45+
<li>
46+
<code>mandate.rejected</code>&nbsp;Due to error or no authorisation,
47+
mandate could not be created
48+
</li>
49+
<li>
50+
<code>mandate.paused</code>&nbsp;Customer has decided to temporarily stop
51+
executions on mandate
52+
</li>
53+
<li>
54+
<code>mandate.revoked</code>&nbsp;Mandate was closed by customer or
55+
merchant before expiry
56+
</li>
57+
<li>
58+
<code>mandate.complete</code>&nbsp;Mandate executions are done, and now
59+
mandate is closed
60+
</li>
61+
</ul>
62+
</Text>

0 commit comments

Comments
 (0)