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 5 Current »

Participants

🔍 Reviewers

Context

We received a request from Iberia to add a new payment method called Ticket Restaurant, which is a meal voucher, the same as Sodexo and Cheque Gourmet. To meet this request, the system must be able to make a payment with a Ticket Restaurant using the card for direct payment from the website or the voucher for physical payment.

Decision

The decision taken for this development was to follow the same logic as the "Sodexo" and "Cheque Gourmet" payments, which for card payments, it uses the same component/logic as payment via credit card, populating a property called paymentMethodBrand for the backend informing whether it is a meal voucher or a normal credit card. And for the voucher that uses the CASH flow/design, populating this same property but with the suffixes "_VOUCHER".

PaymentMethodBrand

VALUE

Sodexo

SODEXO

Sodexo Voucher

SODEXO_VOUCHER

Cheque Gourmet

CHEQUE_GOURMET

Cheque Gourmet Voucher

CHEQUE_GOURMET_VOUCHER

Ticket Restaurant

TICKET_RESTAURANT

Ticket Restaurant Voucher

TICKET_RESTAURANT_VOUCHER

Consequences

As we are reusing credit card components to integrate meal vouchers and the integrations are the same, we will only add a new paymentMethodBrand that will only serve as a demonstration for other subsequent systems such as admin-app, driver-app, DOP , DMP and etc. All other payment systems have already been previously developed, so we will not have any consequences in terms of refunds or adaptations to this new payment method.

  • No labels