Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

formatting changes & diagrams updated #163

Closed
wants to merge 2 commits into from
Closed

formatting changes & diagrams updated #163

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1ca70fb
formatting changes & diagrams updated
Amlan96 Apr 3, 2024
d2b257d
formatting changes
Amlan96 Apr 3, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/payments/umap/mandates/otm.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ visible_in_sidebar: true
</p>
</Card>

<hr class="primary"/>
<br/>

#### What is a One Time Mandate ?

Expand Down
4 changes: 1 addition & 3 deletions content/payments/umap/mandates/otm/check-status.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,7 @@ visible_in_sidebar: true
Read about one time mandate execution, if you haven't already
</p>
</Card>

<hr class="primary"/>

<br/>
The merchant can use the **<i>check status API</i>** to check mandate payment status.

<table>
Expand Down
4 changes: 1 addition & 3 deletions content/payments/umap/mandates/otm/execute.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,7 @@ visible_in_sidebar: true
Read about one time mandate pre debit notification, if you haven't already
</p>
</Card>

<hr class="primary"/>

<br/>
Once the mandate pre debit notification is **successful**, the merchant can execute the mandate on the `executionDate` mentioned while sending the pre debit notification.

The merchant will have to call the **<i>execute mandate API</i>** with the correct set of parameters.
Expand Down
6 changes: 2 additions & 4 deletions content/payments/umap/mandates/otm/pre-debit-notify.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,13 +15,11 @@ visible_in_sidebar: true
Read about one time mandate creation, if you haven't already
</p>
</Card>

<hr class="primary"/>

<br/>
<Callout type="tip">
Pre debit notification is not needed if <code>blockFunds</code> is set as <code>true</code> while creating the mandate.
</Callout>

<br/>
Once the mandate is **LIVE** the merchant needs to send a pre debit notification 48 - 72 Hrs before debit / execution to let the customer be notified of the upcoming debit.

The process for mandate pre debit notification is described in the below diagram:
Expand Down
2 changes: 1 addition & 1 deletion content/payments/umap/mandates/recurring.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ visible_in_sidebar: true
</p>
</Card>

<hr class="primary"/>
<br/>

#### What is a Recurring Mandate ?

Expand Down
2 changes: 1 addition & 1 deletion content/payments/umap/mandates/recurring/check-status.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ visible_in_sidebar: true
</p>
</Card>

<hr class="primary"/>
<br/>

A recurring mandate can have multiple payments associated to it.

Expand Down
6 changes: 3 additions & 3 deletions content/payments/umap/mandates/recurring/create.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -197,7 +197,7 @@ There are 2 ways to create a recurring mandate: **Intent based**, **Collect base
<td>1-7</td>
<td>
<img
src="https://storage.googleapis.com/strapi-assets/latest/recurrence-cropped/recurrence-cropped.png"
src="https://storage.googleapis.com/strapi-assets/latest/Weekly_Recurrence/Weekly_Recurrence.png"
alt="Bridge"
/>
</td>
Expand All @@ -207,7 +207,7 @@ There are 2 ways to create a recurring mandate: **Intent based**, **Collect base
<td>1-16</td>
<td>
<img
src="https://storage.googleapis.com/strapi-assets/latest/recurrence-cropped/recurrence-cropped.png"
src="https://storage.googleapis.com/strapi-assets/latest/Fortnightly_Recurrence/Fortnightly_Recurrence.png"
alt="Bridge"
/>
</td>
Expand All @@ -217,7 +217,7 @@ There are 2 ways to create a recurring mandate: **Intent based**, **Collect base
<td>1-31</td>
<td>
<img
src="https://storage.googleapis.com/strapi-assets/latest/recurrence-cropped/recurrence-cropped.png"
src="https://storage.googleapis.com/strapi-assets/latest/Monthly_and_Above_Recurrence/Monthly_and_Above_Recurrence.png"
alt="Bridge"
/>
</td>
Expand Down
2 changes: 1 addition & 1 deletion content/payments/umap/mandates/recurring/execute.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ visible_in_sidebar: true
</p>
</Card>

<hr class="primary"/>
<br/>

<Callout type="tip">
Merchant intervention is only needed for an execution if <code>autoExecute</code> and <code>autoPreNotify</code> are set to <code>false</code> while creating a mandate
Expand Down
2 changes: 1 addition & 1 deletion content/payments/umap/mandates/recurring/pre-debit-notify.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ visible_in_sidebar: true
</p>
</Card>

<hr class="primary"/>
<br/>

Once the mandate is **LIVE** the merchant needs to send a pre debit notification 48 - 72 Hrs before debit / execution to let the customer be notified of the upcoming debit.

Expand Down
2 changes: 1 addition & 1 deletion content/payments/umap/mandates/single-block-multi-debit.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ visible_in_sidebar: true
</p>
</Card>

<hr class="primary"/>
<br/>

#### What is a Single Block Multi Debit Mandate ?

Expand Down
2 changes: 1 addition & 1 deletion content/payments/umap/mandates/single-block-multi-debit/check-status.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ visible_in_sidebar: true
</p>
</Card>

<hr class="primary"/>
<br/>

A single block multi debit mandate can have multiple payments associated to it.

Expand Down
2 changes: 1 addition & 1 deletion content/payments/umap/mandates/single-block-multi-debit/execute.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ visible_in_sidebar: true
</p>
</Card>

<hr class="primary"/>
<br/>

Once the mandate is **LIVE**, the merchant can execute the mandate whenever a payment is to be collected from the customer.

Expand Down
2 changes: 1 addition & 1 deletion content/payments/umap/merchant-onboarding/check-vpa-availability-api.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ visible_in_sidebar: true

## Check VPA Availability
<Callout type='tip'>This is an optional flow, but to avoid conflicts, check vpa validity before assigning</Callout>

<br/>
VPAs act as unique identifiers in the UPI ecosystem. This item can be used to validate the availability of a VPA to check if it can be associated with a merchant.

<table>
Expand Down
6 changes: 3 additions & 3 deletions content/payments/umap/notifications/customer-vpa-verification.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,11 +9,11 @@ visible_in_sidebar: true

### Verification Statuses

**Customer VPA Valid**: Explain here
**Customer VPA Valid**: VPA provided is valid and associated with a bank account

**Customer VPA Invalid**: Explain here
**Customer VPA Invalid**: VPA provided is invalid and account details could not be fetched

**Customer VPA Failed**: Explain here
**Customer VPA Failed**: Failed to fetch vpa details

### VPA Valid

Expand Down
18 changes: 9 additions & 9 deletions content/payments/umap/refunds-disputes.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,10 +64,10 @@ This comprehensive approach ensures that merchants can efficiently manage refund
<p>In addition to the notifications, merchants can use <b>check refund status API</b> to check if a refund is successful</p>
<hr class="primary"/>
<h4>Refund Statuses</h4>
<li><b>Refund Initiated :</b> Refund request has been create at UMAP</li>
<li><b>Refund Pending :</b> Refund is in queue for being processed</li>
<li><b>Refund Successful :</b> Refund has been successfully completed</li>
<li><b>Refund Failed :</b> Refund could not be processed</li>
<li><code>Refund Initiated :</code> Refund request has been create at UMAP</li>
<li><code>Refund Pending :</code> Refund is in queue for being processed</li>
<li><code>Refund Successful :</code> Refund has been successfully completed</li>
<li><code>Refund Failed :</code> Refund could not be processed</li>
<img
src="https://storage.googleapis.com/strapi-assets/latest/Frame_74/Frame_74.png"
alt="Bridge"
Expand Down Expand Up @@ -113,11 +113,11 @@ This comprehensive approach ensures that merchants can efficiently manage refund
<p>If the merchant does not prevail, a refund is issued to the customer for the disputed transaction.</p>
<hr class="primary"/>
<h4>Dispute Statuses</h4>
<li><b>Dispute Open :</b> A dispute has been created by a customer</li>
<li><b>Dispute Closed :</b> Merchant accepted dispute and issued a refund</li>
<li><b>Dispute In-Review :</b> Merchant has contested dispute and has provided evidence</li>
<li><b>Dispute Won :</b> Merchant evidence accepted. No chargeback required</li>
<li><b>Dispute Lost :</b> Merchant evidence rejected. Chargeback is created </li>
<li><code>Dispute Open :</code> A dispute has been created by a customer</li>
<li><code>Dispute Closed :</code> Merchant accepted dispute and issued a refund</li>
<li><code>Dispute In-Review :</code> Merchant has contested dispute and has provided evidence</li>
<li><code>Dispute Won :</code> Merchant evidence accepted. No chargeback required</li>
<li><code>Dispute Lost :</code> Merchant evidence rejected. Chargeback is created </li>
<img
src="https://storage.googleapis.com/strapi-assets/latest/Frame_73/Frame_73.png"
alt="Bridge"
Expand Down
Loading