Rapyd is a fintech platform offering a large number of financial products, like payments, payouts, or card issuing. Inherently, a lot of this information is often displayed in data tables, like payment transactions, customers, or cards. 

Over time, quick product expansion and customer field requests caused table inconsistencies and clutter. 

I introduced table standardization guidelines and templates to align all tables, and streamline the process of creating new tables. This methodology, while developed for Rapyd, is adaptable across various platforms, specially in Fintech.

The process for new stories, is fairly standard, and usually for new products. At this stage, we will identify key information, relevant actions, review with customers and established guidelines.

In collaboration with our UX team, I embarked on a three-step research exercise: 

Researching first principles and guidelines for data tables, and their applicability to our context; 

This resulted in a set of guidelines and examples for consistent reference and standards for our ongoing and future developments.

The rollout was very smooth. We achieved this, by introducing standardized tables first to new customers, then to existing ones without custom views, while maintaining the current data displays for those with customized views for the time being.

While the framework is broadly applicable, it was developed considering our tech stack and user base. For instance, when we incorporated a specific set of data tables for migrated customers, we opted to maintain their existing structures.

David Shapira

I spearheaded the standardization of financial activity tables and introduced a default template to reduce inconsistencies, streamline processes, and ensure quality.

Describe why we are developing this table, the user problem, and the goal.

Merchants, particularly non-technical users, need a simplified way to monitor their payments. Our goal is to introduce a payments table, streamlining payment tracking, data export, and relevant actions.

💡 When [situation], I want to [motivation], So I can [Expected outcome].

When I want to review all my payment transactions, I want to access a centralized table, so I can efficiently manage and track my payments.

Create a new table under Collect section. The table will have all standard table features, including file export, filters, and customizable columns.

Write the fields that will be added to the table.

Tables can be categorized into two types: transactions (payments, refunds, etc.) and entities (customers, beneficiaries, cards).

In transactions, the amount is first, while in entities, the identifier is usually first.

Created date will be the last default column (rightmost).

The first column should be a human-readable record identifier

The default order of the columns should reflect the importance to the user

Related data should be adjacent to each other.

By default, no more than 7-10 columns should be shown by default.

Boolean fields may not require default states if the default is understood.

For more info view Table guidelines [Link Redacted].

Select frequently searched fields: IDs, names, and merchant references. Reserve attributes like currency and country for filtering instead.

For more info view Search component guidelines [Link Redacted].

The side panel gives a clear summary of the transaction or item, important info from other tables, and relevant actions.

Write the sections and fields to be displayed, empty states, and actions. Sections should include a link to the relevant pages. ID’s should be copyable and clickable.

Write here an audit log for any new action that is performed from the table if applicable - e.g.: exported table.

Add the permissions for which users can see this page and ensure to update the permissions doc - Permissions doc [Link Redacted].

💡 How will we measure success for this feature, and what new events should we include?

For more info Check the Events Dictionary [Link Redacted] for more details and ensure to update it with the new events.

Write the acceptance criteria for this table. Recommended with Given > When > Then format. View pre-made examples below.

 all columns, including default and optional ones, are displayed accurately as specified.

 it matches the text written on this ticket above.

 I should be able to use standard functionalities like

search for payments within the search parameters set above

customize the displayed columns and order

 I select a specific payment record and click on it, 

 the side panel should open, displaying all the relevant details accurately as outlined.

Standardization of Tables at Rapyd

Template - PRD Client Portal New Table

Background & Goal

Job Story

Details

Sign up to see more