Page 1 of 1

Deep link with prefilled fields

Posted: Wed Apr 14, 2021 5:57 pm
by admin_de2
Dear Hugo, dear Roder,

is there an option to have deeplink in Cyclos, as available with EasyInvoice functionality?

e.g.:
https://cyclos-instance.tld/#users.user ... my-profile
=> Calls the profile, it works

https://cyclos-instance.tld/#banking.tr ... -to-system
=> Calls the banking, payment system => user

https://cyclos-instance.tld/?amountFiel ... -to-system
=> Calls the banking, payment system => user as well, but does not prefill the amount field with 100, stays empty

Additional question:
When it's not possible by GET-var (which is probably exclude due to security reasons, isn't it?!?), is it possible then to achive it per script and POST-vars or other technics in the script?!?

Thank you very much,
Th.

PS: Funny, similar but different question from my side 13 years ago... viewtopic.php?f=2&t=235&p=761&hilit=dee ... 3d3c4#p761 here.

Re: Deep link with prefilled fields

Posted: Mon May 10, 2021 12:28 pm
by rmvanarkel
This exactly the easy invoice functionality, I am curious why you just don't use this? Can you eloborate?

Re: Deep link with prefilled fields

Posted: Mon May 17, 2021 5:20 pm
by admin_de2
Dear Roder,

the reason is, that we wanted to offer a menu item called "charge back".
For that reason, a script is called which asks an amount.
The amount is checked if available (means, account-balance has to be at least >= 0 after the transaction, regardless of the user's debit limit).

Then the amount COULD be passed over to usual cyclos payment function, with prefilled fields (receiver, amount).

Since this all happens within a logged in cyclos instance, i didn't think an easy invoice link would work here (and in the app?), since it's not bound and - as far as i know - even excluding it, to a loggin cyclos browser application or cyclos app.

Maybe we should try it, but would expect some strange behavior.

How does the user come back to cyclos afterwards?

If there's another idea, please let me know.
I'll keep you up to date when we tested it.

Thank you, Th.