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
{{ message }}
This repository has been archived by the owner on Feb 10, 2024. It is now read-only.
I am attempting to integrate the Chargily API into my development environment as I believe it offers great functionality for payment processing. However, during testing, I encountered an error while trying to fill up the form in the create-payment view and clicking the submit button.
Error Description:
Upon submitting the form, I am redirected to the fake-payment-view.html page which then indicates the following :
**
TemplateDoesNotExist at /en/epay/fake-payment/17/
chargily_epay_django/fake-payment-view.html **
.
Steps to Reproduce:
Access the development environment.
Navigate to the create-payment view or form.
Fill up the form with the required payment details.
Click the submit button to process the payment.
Expected Behavior:
Upon clicking the submit button in the create-payment form, I expect the form data to be sent to the Chargily API for payment processing. Subsequently, a response should be displayed on the page indicating the payment status or any necessary further action, such as redirection to a payment gateway.
Actual Behavior:
Instead of processing the payment and displaying a relevant response, the form submission redirects to the fake-payment-view.html page, which does not seem to exist in the first place .
Additional Information:
I have followed the sponsor example in the development environment
Possible Solution:
As I am relatively new to integrating external APIs, I suspect there might be an issue in my implementation of the Chargily API or a misconfiguration related the chargily_epay_django/fake-payment-view.html template and handling the API response
. I would greatly appreciate any guidance or insights into the proper way to integrate and utilize the Chargily API in the development environment.
Thank you for your assistance in resolving this issue.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue Description:
I am attempting to integrate the Chargily API into my development environment as I believe it offers great functionality for payment processing. However, during testing, I encountered an error while trying to fill up the form in the create-payment view and clicking the submit button.
Error Description:
Upon submitting the form, I am redirected to the fake-payment-view.html page which then indicates the following :
**
TemplateDoesNotExist at /en/epay/fake-payment/17/
chargily_epay_django/fake-payment-view.html **
.
Steps to Reproduce:
Access the development environment.
Navigate to the create-payment view or form.
Fill up the form with the required payment details.
Click the submit button to process the payment.
Expected Behavior:
Upon clicking the submit button in the create-payment form, I expect the form data to be sent to the Chargily API for payment processing. Subsequently, a response should be displayed on the page indicating the payment status or any necessary further action, such as redirection to a payment gateway.
Actual Behavior:
Instead of processing the payment and displaying a relevant response, the form submission redirects to the fake-payment-view.html page, which does not seem to exist in the first place .
Additional Information:
I have followed the sponsor example in the development environment
Possible Solution:
As I am relatively new to integrating external APIs, I suspect there might be an issue in my implementation of the Chargily API or a misconfiguration related the chargily_epay_django/fake-payment-view.html template and handling the API response
. I would greatly appreciate any guidance or insights into the proper way to integrate and utilize the Chargily API in the development environment.
Thank you for your assistance in resolving this issue.
The text was updated successfully, but these errors were encountered: