The app developer should be able to add Payment component to the layout

[framitdavid]

The first step a service developer needs to enable for supporting payment within their app is to add the Payment component to its layout.

Example of how the configuration looks:

{
  "$schema": "https://altinncdn.no/toolkits/altinn-app-frontend/4/schemas/json/layout/layout.schema.v1.json",
  "data": {
    "layout": [
      {
        "id": "payment-test-component",
        "type": "Payment",
        "textResourceBindings": {
          "title": "Oppsummering"
        },
      }
    ]
  }
}

Why: (Have sent a message to the team apps to ensure my assumptions is correct).
This configuration enables payment functionality within the apps. The component is responsible for displaying payment status and allows the user to proceed with payment or cancel. By setting autoForwardToPayment: true, users will be automatically directed to the payment at Nets.

Needs clarifications

Beta Give feedback

1. Should Studio validate that the Payment layout is added only once per layout-set?

[nkylstad]

If I'm not mistaken, this component should be available only in custom payment layout for the payment step? And will be used by default if the default payment layout if no custom layout is created.

[WilliamThorenfeldt]

Blocked until issue #12809 is solved.

[nkylstad]

Might have to do something with Preview here as well. Possibly simulate that payment is successful? We could expand this to that the app developer could toggle different states for payment status?