Endpoint
This is a browser redirect endpoint. When accessed, it displays a login page for users to authenticate with their DCash credentials.
Query Parameters
Your application’s unique identifier provided during registration
The URL where users will be redirected after authentication
How It Works
This endpoint initiates the OAuth 2.0 authorization flow:1
Redirect User
Your application redirects the user to this DCash URL
2
User Authenticates
User authenticates with their DCash credentials and approves access permissions
3
Token Sent to Webhook
Upon successful authentication, DCash sends an authorization token to your pre-registered webhook endpoint
4
User Redirected
The user is redirected to your specified
redirect_urlAuthorization Token
The token will be sent to the webhook URL configured in your merchant account settings.
- 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 Response
When authentication is successful, your webhook will receive the following payload:Webhook Parameters
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.