This endpoint returns an HTML login page and must be opened in a browser. It cannot be tested via API calls.
Endpoint
Query Parameters
Your application’s unique identifier provided during registration
The URL where users will be redirected after authentication
Try It Out
To test the OAuth flow, construct your URL and open it in a browser:Open OAuth Login (Test)
Opens with test values - modify the URL in your browser’s address bar with your actual credentials
How It Works
This endpoint initiates the OAuth 2.0 authorization flow:Token Sent to Webhook
Upon successful authentication, DCash sends an authorization token to your pre-registered webhook endpoint
Authorization Token
The token will be sent to the webhook URL configured in your merchant account settings, not as a response from this endpoint.
- Store this token securely - it’s required for making API calls on behalf of the user
- Tokens may be revoked by users through the DCash app or website
- If a token becomes invalid, you’ll need to repeat the authorization flow
Security Recommendations
- Always validate that redirect URLs match your expected domain
- Use HTTPS for all redirect URLs
- Store tokens securely using appropriate encryption
Webhook Payload
When authentication is successful, your webhook will receive this payload:Type of event triggered (e.g., “user_authorized”)
Email address of the authenticated user
DCash token for subsequent API requests
Example Webhook Payload
Example Implementation
Here’s how to redirect a user to initiate the OAuth flow:After receiving the token via webhook, you can use it to make authenticated API requests on behalf of the user.