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 4 Next »

Participants

🔍 Reviewers

Context

We received a request from Iberia to refactor two events from amplitude to be possible to identify which type of payment was made. These two events is “Button Click” and “Backend Purchase” that today its only return correctly the payment made via Credit Card and Cash, so the idea is to improve these events to create a better funnel of data.

Decision

We had some meetings to correctly define how this data will be added to these events and it can be found in the table below.

Card Type

Payment Type

Payments available on the platform ( not a log field )

VISA/MASTERCARD

CREDIT_ANONYMOUS

New credit card

VISA/MASTERCARD

VAULTED_ACCOUNT

Vaulted card

CARD

Cash

 

PAYPAL

Paypal

 

APPLE_PAY

Apple pay

 

PAY_CARD_AT_HOME

Pay card at home

 

WAYLET

Waylet

 

BIZUM

Bizum

 

SODEXO_VOUCHER

Sodexo voucher

 

CHEQUE_GOURMET_VOUCHER

Cheque gourmet voucher

 

TICKET_RESTAURANT_VOUCHER

Ticket restaurant voucher

SODEXO_CARD

CREDIT_ANONYMOUS

Sodexo card

CHEQUE_GOURMET_CARD

CREDIT_ANONYMOUS

Cheque gourmet card

TICKET_RESTAURANT_CARD

CREDIT_ANONYMOUS

Ticket restaurant card

Following this table we will create a function to handle each of these payment methods and map them correctly into these two logs. With this, there will be two changes in two repositories, which are whitelabel-app (frontend) and orders-service, which handles the button log and the purchase log, respectively.

Consequences

As a result, we will have these two events with payment methods mapped and it will be possible to create a more effective funnel for these payments, generating sales insights and improving the platform.

  • No labels