get
https://secure.mintpayments.com/mpay/v5/sandbox/openbankingaccountaccess/completegrant/
Completes a sandbox open banking account access authorization flow for testing purposes.
This endpoint simulates the completion of a bank account authorization process without requiring actual bank connections, making it ideal for development and testing environments.
This is a sandbox endpoint that simulates the authorization completion process. In sandbox mode, this endpoint typically returns an HTTP 302 redirect to a success page or custom return URL.
In some cases (e.g., API-only integrations), it may return a 200 JSON response.
Sandbox Authorization Flow
- Initiate: Client calls sandbox access request endpoint to start authorization
- Simulate: Sandbox simulates bank authentication process
- Callback: Sandbox redirects back with simulated authorization code
- Complete: This endpoint simulates token exchange and redirects to success page
Process Overview
This sandbox endpoint will:
- Validate the bank account authorization grant
- Simulate the exchange of authorization code for access tokens
- Simulate secure token storage for future API calls
- Update the authorization grant status to completed
- Redirect the user to a success page or custom return URL
Response Behavior
- Redirect (302): HTTP 302 redirect to success page with grant information (typical web flow)
- JSON (200): JSON response with completion status (API-only integrations)
- Custom Return URL: If provided in initial request, redirects to custom URL
- Error: May redirect to error page with error information
Sandbox Features
- Simulates various success and failure scenarios
- No actual bank connections required
- Predictable responses for testing
- Configurable via query parameters for different test cases
- Safe for development and testing environments
Testing Scenarios
The sandbox supports various testing scenarios:
- Successful authorization completion
- Invalid authorization codes
- Expired grants
- Network simulation errors
- User denial scenarios
Security Considerations
- Sandbox authorization codes are simulated and safe for testing
- No real banking credentials are processed
- Simulated tokens are used for testing purposes only
- Redirect URLs are validated for security even in sandbox mode
- All sandbox data is isolated from production systems
Error Simulation
Common simulated failure scenarios:
- Invalid or expired authorization code
- Mismatched authorization grant
- Simulated API errors
- Simulated network connectivity issues