Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit da92ef5

Browse files
bassgetagitbook-bot
authored andcommitted
GITBOOK-170: feat: add new currencies conversion endpoint docs
1 parent 88e0e4a commit da92ef5

File tree

3 files changed

+22
-1
lines changed

3 files changed

+22
-1
lines changed

docs/request-network-api/crypto-to-fiat-payments.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -56,6 +56,19 @@ Production access includes:
5656

5757
For Crypto-to-fiat Payments, the Request Network API supports USDC on Ethereum, Polygon, Arbitrum One, and Sepolia.
5858

59+
{% hint style="info" %}
60+
**Crypto-to-fiat Payment with non-USDC currencies:**
61+
62+
While crypto-to-fiat requests must be created in USDC, users can pay in alternative currencies through a four-step process, using [crosschain-payments.md](crosschain-payments.md "mention"):
63+
64+
1. **Create Crosschain Request**: Create a request to swap the payer's currency (e.g., ETH on Ethereum) to USDC on the target chain (e.g., USDC on Polygon). Note: Don't specify a payer address during request creation to allow flexibility in who can pay.
65+
2. **Pay Crosschain Request**: Execute the crosschain payment to fulfill the first request
66+
3. **Create Crypto-to-Fiat Request**: Create a separate request for the USDC offramp to fiat and bank deposit
67+
4. **Pay Crypto-to-Fiat Request**: Execute the crypto-to-fiat payment to complete the flow
68+
69+
This four-step approach is required due to current API limitations - more streamlined flows are not yet implemented.
70+
{% endhint %}
71+
5972
## Understanding `clientUserId`
6073

6174
Many `/payer` endpoints in the Request Network API require a `clientUserId` as a path parameter. This value is an **arbitrary identifier** chosen by your platform to represent a user (the payer) in your own system.

docs/request-network-api/recurring-payments.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,9 @@ Recurring payments are supported on the following Blockchain networks:
9999

100100
## Supported currencies
101101

102-
The recurring payments support **all** **ERC20** currencies available in the supported networks
102+
The recurring payments support **all** **ERC20** currencies available in the supported networks.
103+
104+
See the full list here [supported-chains-and-currencies.md](supported-chains-and-currencies.md "mention")
103105

104106
## How it works
105107

docs/request-network-api/supported-chains-and-currencies.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -54,6 +54,8 @@ For Conversion Payments, the Request Network API supports the following _payment
5454
* DAI
5555
* FAU on Sepolia
5656

57+
To get a list of supported _payment_ currencies for a given _invoice_ currency, use the [#get-v2-currencies-currencyid-conversion-routes](supported-chains-and-currencies.md#get-v2-currencies-currencyid-conversion-routes "mention") endpoint.
58+
5759
### Crosschain Payments Supported Currencies
5860

5961
See [#crosschain-payments-supported-chains-and-currencies](crosschain-payments.md#crosschain-payments-supported-chains-and-currencies "mention")
@@ -93,3 +95,7 @@ Each token in the response includes:
9395
{% openapi-operation spec="request-api" path="/v2/currencies" method="get" %}
9496
[OpenAPI request-api](https://api.request.network/open-api/openapi.json)
9597
{% endopenapi-operation %}
98+
99+
{% openapi-operation spec="request-api-staging" path="/v2/currencies/{currencyId}/conversion-routes" method="get" %}
100+
[OpenAPI request-api-staging](https://api.stage.request.network/open-api/openapi.json)
101+
{% endopenapi-operation %}

0 commit comments

Comments
 (0)