Skip to content

Commit

Permalink
edoardo123-PAY-patch-1 fix formatting
Browse files Browse the repository at this point in the history
  • Loading branch information
nlsteers committed Nov 17, 2023
1 parent 8810b53 commit 922237e
Showing 1 changed file with 35 additions and 45 deletions.
80 changes: 35 additions & 45 deletions source/roadmap.html.erb
Original file line number Diff line number Diff line change
Expand Up @@ -11,28 +11,33 @@ title: Roadmap

<div class="govuk-grid-column-two-thirds">
<h1 class="govuk-heading-xl">Roadmap</h1>
<p class="govuk-body">We want to keep making GOV.UK&nbsp;Pay better by adding new features and making sure it's safe and works well for both public sector service teams and paying users.</p>
<div class="govuk-inset-text">
<p class="govuk-body">This is a record of what we've done, and a plan for what we want to improve next. Our plans can change based on what we learn from testing the product and speaking to our users.
We work in 3-monthly cycles.
<p class="govuk-body">
We want to keep making GOV.UK&nbsp;Pay better by adding new features and making sure it's safe and works well for both public sector service teams and paying users.
</p>
<div class="govuk-inset-text">
<p class="govuk-body">
This is a record of what we've done, and a plan for what we want to improve next. Our plans can change based on what we learn from testing the product and speaking to
our users. We work in 3-monthly cycles.
</p>
</div>
<h2 class="govuk-heading-l">Recently released</h2>
<h3 class="govuk-heading-m">Recurring card payments </h3>
<h3 class="govuk-heading-m">Recurring card payments</h3>
<p class="govuk-body">
The first service has started using
<%= link_to 'recurring payments', 'https://docs.payments.service.gov.uk/recurring_payments/', class: 'govuk-link' %> through GOV.UK Pay. Kent County Council are using it for their Trading Standards Checked service. This makes it simpler for people to pay for things regularly and easier for service teams to collect payments. If you're interested in using recurring payments, get in touch.
<%= link_to 'recurring payments', 'https://docs.payments.service.gov.uk/recurring_payments/', class: 'govuk-link' %> through GOV.UK Pay. Kent County Council are using it
for their Trading Standards Checked service. This makes it simpler for people to pay for things regularly and easier for service teams to collect payments. If you're
interested in using recurring payments, get in touch.
</p>
<h3 class="govuk-heading-m">Digital wallets</h3>
<p class="govuk-body">
GOV.UK Pay now lets people pay for local government and police services (using Stripe as their provider) using Apple Pay and Google Pay.
Previously this was only available to central government and NHS services using Worldpay.
Wallets make paying safer and easier, and help more payments go through successfully by reducing mistakes associated with manually typing card information.
GOV.UK Pay now lets people pay for local government and police services (using Stripe as their provider) using Apple Pay and Google Pay. Previously this was only
available to central government and NHS services using Worldpay. Wallets make paying safer and easier, and help more payments go through successfully by reducing mistakes
associated with manually typing card information.
</p>
<h3 class="govuk-heading-m">Data security standard</h3>
<p class="govuk-body">
By passing an assessment called the Payment Card Industry Data Security Standard for 2023, we've made our security stronger.
This takes the complexity of dealing with these rules away from public service teams. It also means that GOV.UK Pay can safely manage personal information when users are making payments.
By passing an assessment called the Payment Card Industry Data Security Standard for 2023, we've made our security stronger. This takes the complexity of dealing with
these rules away from public service teams. It also means that GOV.UK Pay can safely manage personal information when users are making payments.
</p>
<h3 class="govuk-heading-m">Use an external telephone payment system to send card details to the API</h3>
<p class="govuk-body">
Expand All @@ -41,62 +46,47 @@ title: Roadmap
the same way as online payments through GOV.UK&nbsp;Pay.
</p>
<h2 class="govuk-heading-l">What we’re doing now</h2>
<h3 class="govuk-heading-m">Learning about open banking </h3>
<p class="govuk-body">
We're looking at using open banking, which could make payments faster and cheaper while keeping them secure.
</p>
<h3 class="govuk-heading-m">Learning about open banking</h3>
<p class="govuk-body">We're looking at using open banking, which could make payments faster and cheaper while keeping them secure.</p>
<h3 class="govuk-heading-m">Accepting new payment types</h3>
<p class="govuk-body">
Related to the open banking work, we're updating our system to manage not just card payments but other ways to pay as well.
This change is important because it means paying users of government services will have more options, making GOV.UK Pay able to adapt to different needs.
More payment options make it simpler for everyone to use government services in the way that works best for them, and allows more public services to benefit from using us.
We're looking at using open banking, which could make payments faster and cheaper while keeping them secure.
<p class="govuk-body">
Related to the open banking work, we're updating our system to manage not just card payments but other ways to pay as well. This change is important because it means
paying users of government services will have more options, making GOV.UK Pay able to adapt to different needs. More payment options make it simpler for everyone to use
government services in the way that works best for them, and allows more public services to benefit from using us. We're looking at using open banking, which could make
payments faster and cheaper while keeping them secure.
</p>
<h3 class="govuk-heading-m">Accessibility</h3>
<p class="govuk-body">
We're making sure our service can be used by everyone, following the latest Web Content Accessibility Guidelines 2.2 (WCAG 2.2).
</p>
<p class="govuk-body">We're making sure our service can be used by everyone, following the latest Web Content Accessibility Guidelines 2.2 (WCAG 2.2).</p>
<h3 class="govuk-heading-m">Data deletion</h3>
<p class="govuk-body">
We have reviewed our data retention schedules. We continue to make sure personal data is deleted or redacted within 7 years.
</p>
<p class="govuk-body">We have reviewed our data retention schedules. We continue to make sure personal data is deleted or redacted within 7 years.</p>
<h3 class="govuk-heading-m">Database upgrades</h3>
<p class="govuk-body">
We are upgrading 5 of our main databases in GOV.UK Pay to the latest Postgres version.
</p>
<p class="govuk-body">We are upgrading 5 of our main databases in GOV.UK Pay to the latest Postgres version.</p>
<h2 class="govuk-heading-l">What's next</h2>
<h3 class="govuk-heading-m">Recurring payments improvements</h3>
<p class="govuk-body">
We'll use feedback from services and paying users to improve how recurring payments work.
</p>
<p class="govuk-body">We'll use feedback from services and paying users to improve how recurring payments work.</p>
<h3 class="govuk-heading-m">Improving transaction search</h3>
<p class="govuk-body">
We're going to make it easier to find and manage transactions in the admin tool.
</p>
<p class="govuk-body">We're going to make it easier to find and manage transactions in the admin tool.</p>
<h3 class="govuk-heading-m">Strengthening our security</h3>
<p class="govuk-body">
We're getting ready for a new security standard called Payment Card Industry Data Security Standard 4.0 to keep users' information safe.
</p>
<p class="govuk-body">We're getting ready for a new security standard called Payment Card Industry Data Security Standard 4.0 to keep users' information safe.</p>
<h2 class="govuk-heading-l">Future plans</h2>
<h3 class="govuk-heading-m">Procuring new card payment suppliers</h3>
<p class="govuk-body">
We're planning to get the best new card payment suppliers, to make sure service teams and paying users have the best value for money and experience when using GOV.UK Pay.
We're planning to get the best new card payment suppliers, to make sure service teams and paying users have the best value for money and experience when using GOV.UK Pay.
</p>
<h3 class="govuk-heading-m">Improve how we handle data</h3>
<p class="govuk-body">
We're planning to get the best new card payment suppliers, to make sure service teams and paying users have the best value for money and experience when using GOV.UK Pay.
We're planning to get the best new card payment suppliers, to make sure service teams and paying users have the best value for money and experience when using GOV.UK Pay.
</p>
<h3 class="govuk-heading-m">Improve payment reconciliation</h3>
<p class="govuk-body">
We want to simplify the processes with Stripe and Worldpay to help service teams reconcile payments more quickly and efficiently.
</p>
<p class="govuk-body">We want to simplify the processes with Stripe and Worldpay to help service teams reconcile payments more quickly and efficiently.</p>
<h3 class="govuk-heading-m">Annual security checks</h3>
<p class="govuk-body">
We'll continue to stay up to date with our annual PCI compliance evaluations, meeting our commitment to keep our users' payment experience safe and secure.
We'll continue to stay up to date with our annual PCI compliance evaluations, meeting our commitment to keep our users' payment experience safe and secure.
</p>
<h3 class="govuk-heading-m">Linking with other government finance systems</h3>
<p class="govuk-body">
We want to make it easier to connect GOV.UK Pay with Enterprise Resource Planning (ERP) systems. This can reduce the need to manually process data when doing reconciliations and refunds.
We want to make it easier to connect GOV.UK Pay with Enterprise Resource Planning (ERP) systems. This can reduce the need to manually process data when doing
reconciliations and refunds.
</p>
<h4 class="govuk-heading-s">Now</h4>
<p class="govuk-body">Some services are testing the functionality in a private beta sandbox.</p>
Expand Down

0 comments on commit 922237e

Please sign in to comment.