Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Payment Request URL with Stripe Not Working #105

Open
edardev opened this issue Oct 2, 2024 · 7 comments · May be fixed by #106
Open

Payment Request URL with Stripe Not Working #105

edardev opened this issue Oct 2, 2024 · 7 comments · May be fixed by #106

Comments

@edardev
Copy link

edardev commented Oct 2, 2024 •
edited
Loading

I am facing issues sending a payment request URL for Stripe. The URL is not displaying the payment portal, and the format is incorrect in the generated print PDF.

Steps Taken:

I retrieved the payment URL client-side, but it is not functioning either. Here's how I tried to access it:

cur_frm.doc.payment_url
Example output:
https://frontend.com/stripe_checkout?amount=10.6&title=COMPANY&description=Payment+Request+for+ACC-SINV-2024-00001&reference_doctype=Payment+Request&reference_docname=ACC-PRQ-2024-00001&payer_email=edward%40email.com&payer_name=demo-customer&order_id=ACC-PRQ-2024-00001&currency=USD

Problems Encountered:

  1. The payment portal does not appear as expected when using the generated payment request - Stripe URL.
  2. The URL is not formatted correctly in the generated PDF for the payment request.
    image
    image

Despite the Stripe integration setup, the link does not lead to a proper payment interface. Could you please assist in troubleshooting this issue?

Any help in resolving the URL formatting and PDF generation problems would be greatly appreciated.

Thank you!
@edardev edardev changed the title Payment Request URL with Stripe Not Working and Improperly Displayed in PDF Payment Request URL with Stripe Not Working Oct 2, 2024
@blaggacao
Copy link
Collaborator

Can you confirm the commit you're running with, please?

@blaggacao blaggacao linked a pull request Oct 2, 2024 that will close this issue
Open
@blaggacao
Copy link
Collaborator

Please check with #106 — I think I had the same error once in a private branch. [I'm not working at frappe]

@edardev
Copy link
Author

edardev commented Oct 2, 2024

Can you confirm the commit you're running with, please?

I am currently running the latest version, and last night, I created a custom Docker image using the develop branch. The details are as follows:

Commit Hash: 8b57e6d

image

@blaggacao
Copy link
Collaborator

Thanks, I think I already identified the issue. Can you test with the PR, please? Waiting for your feedback on that.

@edardev
Copy link
Author

edardev commented Oct 2, 2024 •
edited
Loading

Thanks, I think I already identified the issue. Can you test with the PR, please? Waiting for your feedback on that.

Thank you for the pull request! I tested it by pulling your PR, but unfortunately, it's still not working as expected. However, when I installed the Payments app on Frappe Cloud, it works perfectly, and the same goes for the Print Designer app.

image
image
image

I'm currently preparing a self-hosted production setup for my first client, and they've been waiting for over two weeks. The discrepancies between the cloud and self-hosted environments are confusing, and I’m struggling to pinpoint the issue.

Any insights or advice on resolving these differences would be greatly appreciated!

@blaggacao
Copy link
Collaborator

Hm, I'm afraid, I'll likely not be able to help, in this case. :-/ — I wouldn't even know where to start.

@edardev
Copy link
Author

edardev commented Oct 3, 2024

Hm, I'm afraid, I'll likely not be able to help, in this case. :-/ — I wouldn't even know where to start.

Thank you for your honesty and taking the time to respond! I appreciate the effort. I'll continue to troubleshoot and explore possible solutions. If anything comes to mind later or if you have any suggestions on where to seek further assistance, feel free to share!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: Decode URL-encoded data in payment gateway files blaggacao/payments
2 participants
@blaggacao @edardev