Skip to content

Conversation

shadyaziza
Copy link

Added new easyPay api

Future<void> easyPay({
    required String checkoutId,
    required BrandType brand,
    required CardInfo card,
  })

Which does not require any configuration from the client side. The possible workflow for this

  1. Request checkoutId from the server
  2. Client manages the values of CardInfo and BrandType entered by the user through a custom payment form
  3. After calling easyPay with the needed data, the client should ask the server about the status of the payment

///
/// [easyPay] does not provide a feedback on the status of payment,
/// since all config is moved to the server; it is the server
/// that should provide a separate api for the mobile application
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
/// that should provide a separate api for the mobile application
/// that should provide a separate API for the mobile application

/// since all config is moved to the server; it is the server
/// that should provide a separate api for the mobile application
/// to request information about the status of a particular transaction.
///
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you add reference links from HyperPay's docs?

@pr-Mais
Copy link
Collaborator

pr-Mais commented May 19, 2023

LGTM, sorry for taking a while to check this PR, well done 👍🏻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants