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.

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

Direct Card Payments API Update #8

Open
Kantonov opened this issue Jul 18, 2024 · 9 comments
Open

Direct Card Payments API Update #8

Kantonov opened this issue Jul 18, 2024 · 9 comments
Assignees
Labels
enhancement New feature or request

Comments

@Kantonov
Copy link

Feature Request

We've changed the API for direct card payments, which must be reflected across SDKs. The documentation can be found here:
https://38fb25f8.api-docs-182.pages.dev/deposit/1.0/#card-payment-integration-2

Also in swagger format:
https://38fb25f8.api-docs-182.pages.dev/swagger/1.0/

@atanasantonov, please contact me at kantonov@zota.com, so I can provide you test credentials and setup for this, also if you have any questions.

@alexbhr please confirm, thanks.

@Kantonov Kantonov added the enhancement New feature or request label Jul 18, 2024
@atanasantonov
Copy link
Collaborator

@Kantonov could you give some hint please if possible what is changed?

@Kantonov
Copy link
Author

@atanasantonov yes. Up until now there was one card request containing card data. This changes as follows:

  1. There is one normal deposit request, without card data, send to a new endpoint, new path.
  2. The responded URL is the one where another request must be sent containing only card data.

To the SDK users this should be implemented seamlessly. So they can provide one payload (set of parameters), and we make those 2 requests happen in the background. At the end just returning the final result, the response from the second request, given everything went smoothly without errors.

@alexbhr
Copy link
Contributor

alexbhr commented Aug 28, 2024

@atanasantonov can this be addressed so we can ship an updated SDK?

@atanasantonov
Copy link
Collaborator

@alexbhr i have dropped an email on 27.07 becasue there was issues and as per your email from 06.08 waiting for @Kantonov to be back from vacation to bring light. The email as follows:

Notes to mention:

  1. There is little mismatch between the documentation and Swagger for Deposit Card - In Swagger the Deposit Card Flow body contains the card data.
  2. No matter what card is used (Test Cards V1 / V2) without 3D secure the response is some HTML with the message We're sorry but payment-page doesn't work properly without JavaScript enabled. Please enable it to continue.
  3. We can login as SDKexplorer in https://dashboard.zota-sandbox.com/ but we cant see the test orders there.

Questions:

  1. What it means the response We're sorry but payment-page doesn't work properly without JavaScript enabled. Please enable it to continue.?
  2. Is it a way we can see the orders in the Sandbox dashboard?

@Kantonov
Copy link
Author

@atanasantonov sorry for the delay, I've responded via email, let me know if everything is answered 🙏

@atanasantonov
Copy link
Collaborator

@Kantonov ok, thanks. I haven't received anything and the reply it's probably to Milen. @gonzomir can you confirm please?

@gonzomir
Copy link
Collaborator

gonzomir commented Oct 2, 2024

@atanasantonov That comment above is from Aug 30, my email is from Sep 5 and I haven't received anything yet.

@atanasantonov
Copy link
Collaborator

@gonzomir ouch for some reason there was an unread email in my Github folder and I clicked the link to the issue. And because we are expecting an answer totally missed the date.. Anyway it will be notification to others.

@Kantonov
Copy link
Author

Kantonov commented Oct 3, 2024

@gonzomir @atanasantonov, hope you received my email from today (3 Oct) regarding the 400 bad request issue 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants