Merge pull request #2175 from SwedbankPay/feature/devp-347_release_pr…

…ep_for_5_0_0

DEVP-347: cleanup before release 5.0.0

Gemfile

@@ -14,7 +14,7 @@ group :jekyll_plugins do
   gem 'kramdown', '>= 2.3'
   gem 'kramdown-plantuml', '>= 1.3'
   gem 'rouge', '>= 4.0.1'
-  gem 'swedbank-pay-design-guide-jekyll-theme', '2.2.6'
+  gem 'swedbank-pay-design-guide-jekyll-theme', '2.2.7'
 end
 
 group :test do

Gemfile.lock

@@ -162,7 +162,7 @@ GEM
     sass-listen (4.0.0)
       rb-fsevent (~> 0.9, >= 0.9.4)
       rb-inotify (~> 0.9, >= 0.9.7)
-    swedbank-pay-design-guide-jekyll-theme (2.2.6)
+    swedbank-pay-design-guide-jekyll-theme (2.2.7)
       awesome_print
       faraday (>= 1.0.1, < 3)
       jekyll (>= 3.7, < 5.0)
@@ -205,7 +205,7 @@ DEPENDENCIES
   rspec (>= 3)
   rubocop (>= 1)
   rubocop-rake (>= 0.6)
-  swedbank-pay-design-guide-jekyll-theme (= 2.2.6)
+  swedbank-pay-design-guide-jekyll-theme (= 2.2.7)
 
 RUBY VERSION
    ruby 2.7.2p137

_includes/one-click-payments.md

@@ -319,11 +319,13 @@ Content-Type: application/json;version=3.1/3.0/2.0      // Version optional for
 
 {% if documentation_section contains "checkout-v3" %}
 
-## Consent Checkbox For Instrument Mode And Custom Menu Selections
+## Disable Store Details and Toggle Consent Checkbox
+
+This is a feature intended for instrument mode and or custom menus.
 
 If you have built your own interface to display previously stored details and
 generate transactions using them ("One-Click Request Displaying A Specific
-Card"), you will have the need to include an option for them to store new
+Card"), you will also  have the need to include an option for them to store new
 details. This can be performed using either a `Purchase` or `Verify` operation.
 
 For `Purchase` operations aiming to store new details simultaneously, you will
@@ -376,7 +378,6 @@ in a validation error.
 
 ## How It Looks
 
-
 {% include alert.html type="informative" icon="info" body="
 When redirecting to Swedbank Pay the payment page will be
 prefilled with the payer's card details. See example below." %}

_includes/payment-link.md

@@ -229,8 +229,8 @@ sequenceDiagram
 [card-payment]: /assets/img/payments/card-payment.png
 [card]: /old-implementations/payment-instruments-v1/card
 [checkout-v2]: /old-implementations/checkout-v2/
-[checkout-v3]: /checkout-v3/payment-request/
-[checkout-v31]: /checkout-v3/payment-request-3-1/
+[checkout-v3]: /checkout-v3/get-started/payment-request/
+[checkout-v31]: /checkout-v3/get-started/payment-request-3-1/
 [mobilepay]: /old-implementations/payment-instruments-v1/mobile-pay
 [payment-menu]: /old-implementations/payment-menu-v2
 [purchase-flow]: /old-implementations/payment-instruments-v1/card/features/core/purchase

_includes/sort-order-payment-menu.md

@@ -10,7 +10,7 @@ an Apple device? Put Apple Pay first. Use the `Paid` resource to find what
 instrument the customer used to pay, and let it be the first option next time
 they visit you.
 
-## Sort And Restrict The Payment Menu Order
+## Sort Or Restrict The Payment Menu Order
 
 Choosing the order is very easy. You simply add the `array` field
 `restrictedToInstruments`, and the order you enter the payment instruments is
@@ -30,8 +30,9 @@ presented in the default order.
 
 ## Input Values
 
-The list of possible values to include in `restrictedToInstruments` are the
-following, depending on which payments instruments you have active.
+The complete list of possible values to include in `restrictedToInstruments` are
+the following. You can find the instruments activated for your merchant
+under `availableInstruments` in the initial `paymentOrder` response.
 
 {:.table .table-striped}
 | Payment Instrument    | Input             |
@@ -64,9 +65,6 @@ Neither `expandFirstInstrument` or `restrictedToInstruments` will be visible in
 the **response**, so we will not include it here. The response will look like
 a basic `paymentOrder` response.
 
-{:.code-view-header}
-**Request**
-
 {% capture request_header %}POST /psp/paymentorders HTTP/1.1
 Host: {{ page.api_host }}
 Authorization: Bearer <AccessToken>

_includes/use-case-one-click.md

@@ -4,11 +4,11 @@
 Looking to get started with One-Click or "Payer Aware Menu" to reduce
 friction? These are the supported instruments:
 
-* Cards: Masked PAN, Expiration Date and CVC
-* Swish: MSIDSN – Only for eCom-flow
-* Vipps: MSIDSN
-* Invoice: Email and MSIDSN
-* Trustly: Preferred bank account
+*   Cards: Masked PAN, Expiration Date and CVC
+*   Swish: MSIDSN – Only for eCom-flow
+*   Vipps: MSIDSN
+*   Invoice: Email and MSIDSN
+*   Trustly: Preferred bank account
 
 ## Introduction
 
@@ -32,17 +32,20 @@ To enable storing details for future purchases using the Payer Aware Menu,
 follow these steps:
 
 1.  Parameter `generatePaymentToken`:
-* Set to `true` inside the payment order request.
-* This value remains `true` by default for all transactions unless you wish to
+
+*   Set to `true` inside the payment order request.
+*   This value remains `true` by default for all transactions unless you wish to
   force “Guest mode”; in that case, send `false`.
 
 2.  Payer Object:
-* Include the parameter `payerReference`. Assign a unique value that can be sent
+
+*   Include the parameter `payerReference`. Assign a unique value that can be sent
 with every future transaction. Failure to send in the same reference may result
 in wrong details being displayed or defaulting to creating a new profile.
 
 3.  Optional Enhancements:
-* Expand the `Payer` object with additional information such as first and last
+
+*   Expand the `Payer` object with additional information such as first and last
 name, phone number and email address. This data will pre-populate relevant
 fields, providing a seamless experience for customers.
 
@@ -54,14 +57,17 @@ Menu documentation.
 To get started with One-Click payments, follow these steps:
 
 1.  Parameter `generatePaymentToken`:
-* Set to `true` inside the payment order request for initial storing of details.
+
+*   Set to `true` inside the payment order request for initial storing of details.
 
 2.  For Future Transactions:
-* Modify the `generatePaymentToken` parameter into `paymentToken` instead and
+
+*   Modify the `generatePaymentToken` parameter into `paymentToken` instead and
 replace the value `true` with the GUID (tokenized reference of the card) value.
 
 3.  Optional Enhancements:
-* Just like with “Payer Aware Menu”, you can enhance the payment experience by
+
+*   Just like with “Payer Aware Menu”, you can enhance the payment experience by
 submitting relevant fields in the `Payer` object to pre-populate relevant
 fields.
 
@@ -144,13 +150,13 @@ When certain conditions arise, such as encountering specific error codes or
 receiving requests from the payer to remove their details, it becomes necessary
 to initiate the deletion of associated tokens. Here are two methods:
 
-* Deletion of all Tokens:
+*   Deletion of all Tokens:
 Send a `PATCH` call to the base URL with the endpoint
 `/psp/paymentorders/payerOwnedTokens/<payerReference>`.
 
 This operation is only available for “Payer Aware Menu”.
 
-* Deletion of a singular Token:
+*   Deletion of a singular Token:
 Use the URL `/psp/paymentorders/paymenttokens/<TokenValue>`.
 
 Both scenarios generate the same response:
@@ -167,10 +173,10 @@ Both scenarios generate the same response:
 
 ## Common causes that triggers the need for deletion
 
-* Your customer requests their information to be removed.
-* Your agreement with your customer has been terminated or expired.
-* Error codes pertaining to permanent causes. Example of these can be
+*   Your customer requests their information to be removed.
+*   Your agreement with your customer has been terminated or expired.
+*   Error codes pertaining to permanent causes. Example of these can be
   `Card Expired (54)` or `Card stolen (43)`
 
-[oc1]: /assets/img/OC1.png
-[pam1]: /assets/img/PAM1.png
+[oc1]: /assets/img/OC1.JPG
+[pam1]: /assets/img/PAM1.JPG

checkout-v3/features/optional/delete-token.md

@@ -2,7 +2,7 @@
 title: Delete Token
 permalink: /:path/delete-token/
 description: How to delete tokens.
-menu_order: 1800
+menu_order: 1900
 icon:
   content: delete_sweep
   outlined: true

checkout-v3/features/optional/fees-discounts.md

@@ -3,7 +3,7 @@ title: Fees And Discounts
 permalink: /:path/fees-discounts/
 description: |
   How to add fees and discounts to payment orders.
-menu_order: 1900
+menu_order: 2000
 icon:
   content: discount
   outlined: true

checkout-v3/features/optional/instrument-mode.md

@@ -2,7 +2,7 @@
 title: Instrument Mode
 permalink: /:path/instrument-mode/
 description: The Payment Menu with one payment instrument
-menu_order: 2000
+menu_order: 2100
 icon:
   content: looks_one
   outlined: true

checkout-v3/features/optional/integrated-commerce.md

@@ -2,7 +2,7 @@
 title: Integrated Commerce
 permalink: /:path/integrated-commerce/
 description: A printable, scannable reference code for payment tracking.
-menu_order: 2100
+menu_order: 2200
 icon:
   content: document_scanner
   outlined: true

checkout-v3/features/optional/moto.md

@@ -3,7 +3,7 @@ title: MOTO
 permalink: /:path/moto/
 description: |
   Mail Order / Telephone Order transactions.
-menu_order: 2200
+menu_order: 2300
 icon:
   content: dns
   outlined: true

checkout-v3/features/optional/network-tokenization.md

@@ -2,7 +2,7 @@
 title: Network Tokenization
 permalink: /:path/network-tokenization/
 description: Stored cards made easier
-menu_order: 2300
+menu_order: 2400
 icon:
   content: share
   outlined: true

checkout-v3/features/optional/one-click-payments.md

@@ -3,7 +3,7 @@ title: One-Click Payments
 permalink: /:path/one-click-payments/
 description: |
   Prefilling the payment details using payment tokens.
-menu_order: 2400
+menu_order: 2500
 icon:
   content: touch_app
   outlined: true

checkout-v3/features/optional/order-items.md

@@ -2,7 +2,7 @@
 title: Order Items
 permalink: /:path/order-items/
 description: Information about the order items
-menu_order: 2500
+menu_order: 2600
 icon:
   content: article
   outlined: true

checkout-v3/features/optional/payer-aware-payment-menu.md

@@ -3,7 +3,7 @@ title: Payer Aware Payment Menu
 permalink: /:path/payer-aware-payment-menu/
 description: |
   A payment menu tailored to the payer.
-menu_order: 2600
+menu_order: 2700
 icon:
     content: event
     outlined: true

checkout-v3/features/optional/payer-restrictions.md

@@ -3,7 +3,7 @@ title: Restricted To SSN
 permalink: /:path/payer-restrictions/
 description: |
   Restricting payments to a specific Social Security Number (SSN)
-menu_order: 2700
+menu_order: 2800
 icon:
   content: lock
   outlined: true

checkout-v3/features/optional/payment-link.md

@@ -3,7 +3,7 @@ title: Payment Link
 permalink: /:path/payment-link/
 description: |
   Sending the payment via mail or SMS.
-menu_order: 2800
+menu_order: 2900
 icon:
   content: link
   outlined: true

checkout-v3/features/optional/payout.md

@@ -2,7 +2,7 @@
 title: Payout
 permalink: /:path/payout/
 description: Paying out funds to the consumer's account.
-menu_order: 2900
+menu_order: 3000
 icon:
   content: euro_symbol
   outlined: true

checkout-v3/features/optional/recur.md

@@ -3,7 +3,7 @@ title: Recur
 permalink: /:path/recur/
 description: |
   Setting up subscriptions and recurring payments.
-menu_order: 3000
+menu_order: 3100
 icon:
   content: cached
   outlined: true

checkout-v3/features/optional/request-delivery-info.md

@@ -3,7 +3,7 @@ title: Request Delivery Information
 permalink: /:path/request-delivery-info/
 description: |
   Request that payment instruments return delivery information.
-menu_order: 3100
+menu_order: 3200
 icon:
   content: local_shipping
   outlined: true

checkout-v3/features/optional/sort-order-payment-menu.md

@@ -1,9 +1,9 @@
 ---
-title: Sort And Restrict Order Of Payment Menu
+title: Customize Order Of Payment Menu
 permalink: /:path/sort-order-payment-menu/
 description: |
-  Customize the order of options in your payment menu
-menu_order: 3200
+  Sort the order of and restrict your payment menu
+menu_order: 1800
 icon:
   content: format_list_numbered
   outlined: true

checkout-v3/get-started/index.md

@@ -1,7 +1,7 @@
 ---
 section: Get Started
 sidebar_icon: description
-title: Introduction
+title: The Basics
 description: |
   Everything you need to set up a basic payment integration
 permalink: /:path/

checkout-v3/release-notes.md

@@ -984,7 +984,7 @@ integration and the payer.
 [checkout-v3-payments-only-redirect-request]: /checkout-v3/get-started/payment-request
 [checkout-v3-payments-only-seamless]: /checkout-v3/get-started/display-payment-ui/seamless-view
 [click-to-pay]: /checkout-v3/payment-presentations#click-to-pay
-[consent-box]: /checkout-v3/features/optional/one-click-payments/#enable-payment-details-consent-checkbox
+[consent-box]: /checkout-v3/features/optional/one-click-payments/#disable-store-details-and-toggle-consent-checkbox
 [contact-us]: /#front-page-contact-partners
 [co-badge-card]: /old-implementations/payment-instruments-v1/card/features/optional/cobadge-dankort#co-badge-card-choice-for-dankort
 [core-features]: /old-implementations/checkout-v2/features/core/