Skip to main content
ggCircuit
Back to all posts

QR Code Display for Stripe Payment Processing in Web Admin

QR Code Display for Stripe Payment Processing in Web Admin illustration

User Story:
As an employee working in the ggLeap Web Admin shop interface, I need the ability to select Stripe as a payment method and show a QR code to the customer so that the payment process is consistent with the experience provided in the ggLeap Client.

​

Acceptance Criteria:

  1. QR Code Generation:

    • When an employee selects Stripe as the payment method during a transaction in the Web Admin shop, a QR code should be automatically generated.

    • The QR code should be unique to the transaction and should encode the payment information required by Stripe.

  2. Payment Confirmation:

    • After the customer scans the QR code with their device, they should be able to complete the payment using Stripe's interface.

    • The Web Admin interface must update in real-time, reflecting the payment status as pending, completed, or failed based on the response from Stripe.

  3. Transaction Continuity:

    • The transaction should not be completed in the Web Admin until confirmation of payment is received from Stripe.

    • In the event of a payment failure, the employee should be prompted with an option to retry the payment or choose a different payment method.

  4. Receipt Generation:

    • Upon successful payment, a receipt should be generated in ggLeap Web Admin which includes the transaction details and payment method used.

    • The receipt number in ggLeap should correspond with the transaction record in Stripe for easy reconciliation.

  5. Security and Compliance:

    • No credit card or payment details should be handled or stored in the Web Admin. All sensitive information must be processed within Stripe to comply with PCI DSS standards.

  6. Error Handling:

    • If there are any errors during the QR code generation or payment process, clear error messages should be displayed to the employee.

    • There should be a fallback option for manual payment processing in case of system failures.

  7. Training and Documentation:

    • Documentation should be provided on how to process payments using the QR code system.

    • Staff should be trained on the new process to ensure a smooth transition for customers.

Out of Scope:

  • Integrating other payment methods through the QR code system is not part of this user story.

  • Changes to the Stripe payment processing system itself are out of scope, as it is a third-party service.

Comments0