---
id: object/table/1060
type: object
title: Table 1060 "Payment Service Setup"
summary: Table 1060 "Payment Service Setup" in Base Application (Microsoft.Bank.Setup). 10 fields, 14 public procedures, 6 events. Present since at least BC23, still in BC30, changed in BC24, BC28.
tier: official
language: en
tags:
  - table
  - base application
versions:
  introduced: null
  last_changed: "28"
  deprecated: null
review:
  state: derived
  by: null
  at: null
  flags: []
generated:
  at: "2026-10-11T00:31:51.816Z"
  pipeline: 0.2.0
  prompts: {}
  input_hash: 18819c4c32893474c603f34c4a06e01cffb9e4504747f751e551bd8b580759d3
evidence:
  - kind: code
    url: https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Bank/Setup/PaymentServiceSetup.Table.al
    title: src/Layers/W1/BaseApp/Bank/Setup/PaymentServiceSetup.Table.al (releases/29.x)
    date: null
    commit: ea08af5ef2d6a9b5c5af4a029288abbe2c883220
    t: null
    quote: null
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
object_type: table
object_id: 1060
name: Payment Service Setup
namespace: Microsoft.Bank.Setup
app: Base Application
extends: null
first_version: "23"
last_version: "30"
present_in:
  - "23"
  - "24"
  - "25"
  - "26"
  - "27"
  - "28"
  - "29"
  - "30"
changed_in:
  - "24"
  - "28"
source_major: "29"
obsolete: null
countries: []
ms_search_form_ids: []
counts:
  fields: 10
  procedures: 24
  events: 6
  subscribers: 0
relations:
  out: 0
  referenced_by: 0
  pages: 3
  extended_by: 0
  event_subscribers: 4
  calls: 5
  called_by: 0
  implements: 0
---

# Table 1060 "Payment Service Setup"

> Table 1060 "Payment Service Setup" in Base Application (Microsoft.Bank.Setup). 10 fields, 14 public procedures, 6 events. Present since at least BC23, still in BC30, changed in BC24, BC28.

Base Application · Microsoft.Bank.Setup · BC23-30 · [source at ea08af5e](https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Bank/Setup/PaymentServiceSetup.Table.al) · facts from BC29

## Properties

| Property | Value |
|---|---|
| Caption | Payment Service Setup |
| DataClassification | CustomerContent |
| Permissions | TableData "Sales Invoice Header" = rimd, TableData "Payment Reporting Argument" = rimd |

## Fields

Explanation: the field's ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.

| No. | Name | Type | Explanation | Notes |
|---|---|---|---|---|
| 1 | No. | Text[250] | — |  |
| 2 | Name | Text[250] | Specifies the name of the payment service. | NotBlank |
| 3 | Description | Text[250] | Specifies the description of the payment service. | NotBlank |
| 4 | Enabled | Boolean | Specifies that the payment service is enabled. |  |
| 5 | Always Include on Documents | Boolean | Specifies that the payment service is always available in the Payment Service field on outgoing sales documents. |  |
| 6 | Setup Record ID | RecordID | — |  |
| 7 | Setup Page ID | Integer | — |  |
| 8 | Terms of Service | Text[250] | Specifies a link to the Terms of Service page for the payment service. | not editable |
| 100 | Available | Boolean | Specifies that the icon and link to the payment service will be inserted on the outgoing sales document. |  |
| 101 | Management Codeunit ID | Integer | — |  |

## Keys

- Key1: No. (clustered)

## Events published

- `OnRegisterPaymentServices(var PaymentServiceSetup: Record "Payment Service Setup")` (integration): Integration event for registering available payment services in the system. Enables extensions to add custom payment service configurations.
  - subscribers: [Codeunit 1070 "MS - PayPal Standard Mgt."](../codeunit/1070.md) RegisterPayPalStandardAccounts
- `OnRegisterPaymentServiceProviders(var PaymentServiceSetup: Record "Payment Service Setup")` (integration): Integration event for registering payment service providers and their capabilities. Allows extensions to define new payment provider types and configurations.
  - subscribers: [Codeunit 1070 "MS - PayPal Standard Mgt."](../codeunit/1070.md) RegisterPayPalStandardTemplateOnRegisterPaymentServiceProviders
- `OnBeforeCanUsePaymentMethod(PaymentMethodCode: Code[10]; var Result: Boolean; var IsHandled: Boolean)` (integration): Integration event raised before checking if a payment method can be used. Enables custom validation logic for payment method availability.
- `OnCreatePaymentService(var PaymentServiceSetup: Record "Payment Service Setup")` (integration): Integration event for custom payment service creation logic. Allows extensions to perform additional setup when creating payment services.
  - subscribers: [Codeunit 1070 "MS - PayPal Standard Mgt."](../codeunit/1070.md) NewPaymentAccount
- `OnDoNotIncludeAnyPaymentServicesOnAllDocuments()` (integration): Integration event raised when removing payment services from all documents. Enables custom cleanup logic when disabling payment service integration.
  - subscribers: [Codeunit 1070 "MS - PayPal Standard Mgt."](../codeunit/1070.md) HandleOnDoNotIncludeAnyPaymentServicesOnAllDocuments
- `OnCanChangePaymentServiceOnAfterGetRecordRef(DocumentVariant: Variant; DocumentRecordRef: RecordRef; var Result: Boolean; var IsHandled: Boolean)` (integration): Integration event raised after determining document context for payment service changes. Enables custom validation logic for payment service modification permissions.

## Procedures

- `OpenSetupCard()`: Opens the setup card page for this payment service configuration. Allows users to modify provider-specific settings and parameters.
- `CreateReportingArgs(var PaymentReportingArgument: Record "Payment Reporting Argument"; DocumentRecordVariant: Variant)`: Creates payment reporting arguments for a specific document and its associated payment services. Generates the data needed for payment provider integration and customer communication.
- `GetDefaultPaymentServices(var SetID: Integer): Boolean`: Retrieves payment services configured to be always included on documents. Returns a set ID for enabled payment services that are set to be included by default.
- `SelectPaymentService(var SetID: Integer): Boolean`: Presents payment service selection dialog to user and returns the selected set ID. Handles the complete workflow for selecting payment services including setup prompts.
- `SaveSet(var TempPaymentServiceSetup: Record "Payment Service Setup" temporary): Integer`: Saves a temporary payment service setup collection as a persistent set. Converts temporary payment service records into a record set that can be referenced by ID.
- `LoadSet(var TempPaymentServiceSetup: Record "Payment Service Setup" temporary; SetID: Integer)`: Loads a payment service set into temporary records based on the provided set ID. Marks payment services as available based on their inclusion in the specified set.
- `GetSelectedPaymentsText(SetID: Integer): Text`: Returns a comma-separated text string of selected payment service names. Provides user-friendly display of payment services included in a set.
- `CanChangePaymentService(DocumentVariant: Variant): Boolean`: Determines if payment service configuration can be changed for a given document. Validates document status and payment method compatibility for payment service modifications.
- `ChangePaymentServicePostedInvoice(var SalesInvoiceHeader: Record "Sales Invoice Header")`: Enables changing payment service configuration for a posted sales invoice. Updates the payment service set ID on the posted invoice and provides user feedback.
- `IsPaymentServiceVisible(): Boolean`: Checks if payment services are available for display in user interfaces. Determines visibility of payment service functionality based on registered providers.
- `NewPaymentService(): Boolean`: Initiates creation of a new payment service through the setup workflow. Handles provider selection and setup dialog presentation to the user.
- `AssignPrimaryKey(var PaymentServiceSetup: Record "Payment Service Setup")`: Assigns the primary key for a payment service setup record based on its setup record ID. Ensures unique identification of payment service configurations.
- `DeletePaymentServiceSetup(RunTrigger: Boolean)`: Deletes the underlying payment service setup record referenced by the Setup Record ID. Performs cleanup of related configuration data when removing payment services.
- `TermsOfServiceDrillDown()`: Opens the Terms of Service URL in the default browser or application. Enables users to review payment service provider terms and conditions.

Plus 4 local procedures.

## Triggers

OnDelete

## Pages and codeunits on this table

- [Page 1060 "Payment Services"](../page/1060.md) (source table)
- [Page 1061 "Select Payment Service"](../page/1061.md) (source table)
- [Page 1062 "Select Payment Service Type"](../page/1062.md) (source table)

## Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an `Object::"Name"` argument. Interface dispatch and calls through events are not counted, so the list is not complete.

- [Codeunit 701 "Data Type Management"](../codeunit/701.md) (6 calls: `CanChangePaymentService → FindFieldByName`, `CanChangePaymentService → GetRecordRef`, `CreateReportingArgs → FindFieldByName`, …)
- [Codeunit 8400 "Record Set Management"](../codeunit/8400.md) (4 calls: `GetDefaultPaymentServices → GetSet`, `GetDefaultPaymentServices → SaveSet`, `LoadSet → GetSet`, …)
- [Page 1060 "Payment Services"](../page/1060.md) (1 call: `AskUserToSetupNewPaymentService → (object)`)
- [Page 1061 "Select Payment Service"](../page/1061.md) (1 call: `SelectPaymentService → (object)`)
- [Page 1062 "Select Payment Service Type"](../page/1062.md) (1 call: `NewPaymentService → (object)`)

## Across versions

- Present in: BC23-30
- Changed (declaration) in: BC24, BC28

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

## Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: `bcatlas_resolve_node(object_type: "table", object_name: "Payment Service Setup")`, then `bcatlas_get_procedure_body` or `bcatlas_get_neighbors` on the returned id.