Change Details

This use case is for external payment providers like paypal. When the user is finished paying there, he should be redirected back to the confirmation page. GET request Request params: - Donation ID - Access Token (to avoid leaking personal info when a user just tries out different donation IDs) When the donation ID with the matching access token is found, display the same confirmation page template as in the "Add donation" use case, with the same response model.

This use case is for external payment providers like paypal. When the user is finished paying there, he should be redirected back to the confirmation page. GET request Request params: - Donation ID - Access Token (to avoid leaking personal info when a user just tries out different donation IDs) When the donation ID with the matching access token is found, display the same confirmation page template as in the "Add donation" use case, with the same response model (minus the error state).

This use case is for external payment providers like paypal. When the user is finished paying there, he should be redirected back to the confirmation page. GET request Request params: - Donation ID - Access Token (to avoid leaking personal info when a user just tries out different donation IDs) When the donation ID with the matching access token is found, display the same confirmation page template as in the "Add donation" use case, with the same response model (minus the error state).