You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/request-network-api/crypto-to-fiat-payments.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ Crypto-to-fiat payments let a payer pay a Request in cryptocurrency, while the p
14
14
15
15
[EasyInvoice](easyinvoice-api-demo-app.md) includes a reference implementation for this flow.
16
16
17
-
###Understanding `clientUserId`
17
+
## Understanding `clientUserId`
18
18
19
19
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.
20
20
@@ -33,7 +33,7 @@ GET /v2/payer/{clientUserId}/payment-details
33
33
34
34
In each case, replace `{clientUserId}` with your chosen identifier for the user.
35
35
36
-
## 1. Compliance & Payer Onboarding
36
+
## Compliance & Payer Onboarding
37
37
38
38
Before a payer can use crypto-to-fiat, they must complete compliance steps:
39
39
@@ -87,7 +87,7 @@ sequenceDiagram
87
87
[Broken link](broken-reference)
88
88
{% endopenapi-operation %}
89
89
90
-
### 2. Setting Up a Crypto-to-Fiat Request (Payee Flow)
90
+
## Setting Up a Crypto-to-Fiat Request (Payee Flow)
91
91
92
92
Before a payer can pay in crypto and the payee can receive fiat, the platform must:
93
93
@@ -142,7 +142,7 @@ In EasyInvoice, the Payee Bank Account Registration is integrated directly into
142
142
[Broken link](broken-reference)
143
143
{% endopenapi-operation %}
144
144
145
-
## 3. Paying a Crypto-to-Fiat Request
145
+
## Paying a Crypto-to-Fiat Request
146
146
147
147
The payer pays in crypto; Request Tech handles offramping and fiat payout.
0 commit comments