Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 29 Next »

Table of Contents

Business problems to be solved

Payment at home represents 41% of the payments in Portugal today. With that in mind, this is a crucial feature for our customers to guarantee the best experience. The idea is to deliver a new method of payment (that we'll call here "Card at home"). To see more details: Feature - Payment with card at home

Proposed solution

Configure “card at home” using the CASH payment method and CARD_AT_HOME payment method brand as an option. This was the solution used to implement Sodexo and Cheque Gourmet vouchers, which allowed us to take advantage of the groundwork laid by it: /wiki/spaces/IN/pages/3932717313

Pros and cons

Pros

  • Require small changes since the structure is very similar to Sodexo and Cheque Gourmet vouchers

    • Reuse of components and structures that already exists on the code

  • Avoids the complexity of creating a new payment method from scratch, which impact many repositories and integrations

Cons

  • Since Winrest processes payment using paymentMethod field, it can’t differentiate between cash, voucher, or “card at home” payments

Out of scope

  • Saving the Card brand used for “Card at home” payments for future reports. This information is not saved today.

Design analysis

Whitelabel proposed changes

PS: click on the images below to open (I don’t want to flood the document with big images).

Account payment methods

Method payment selection

Order confirmation

As the flow will be similar to the payment with cash option we believe that we'll not need to change many details on this screen and we'll just change the information about the payment method.

Tracking modal

Email receipt

I think that we'll need to return the payment method description for this new method. A possibility about this email template is that it is controlled/used in Amazon SNS. I'll validate this with Caes, Guilherme.

Technical discovery

Architecture AS-IS

Winrest integration

To configure the integration with Winrest team, we’ll need to send them the exact string of the new payment method so they can configure it on their platform (Aligned with Paulo Silva). The drawback of using payment type as CASH and a new payment method brand (eg. CARD_AT_HOME) is that the integration still works, but in Winrest reports these payments will be included as cash.

Necessary changes

intl-packages

intl-fulfillment-service

  • Update intl-packages versions

intl-payment-service

  • Update intl-packages versions

intl-whitelabel-graphql

          ...
          const isSodexoOrChequeGourmet = !!payment?.paymentMethodBrand;

          // we set the status to PAYMENT_REQUIRED for cash
          if ((isCashPayment && cashPaymentEnabled) || isSodexoOrChequeGourmet) {
            const updatedCart = {
              ...updatedOrder.cart,
              payment: {
                cardType,
                paymentMethodBrand: payment?.paymentMethodBrand || undefined,
              },
            } as ICart;
            ...

intl-whitelabel-app

  • No labels