Table 1060 "Payment Service Setup"

Base Application · Microsoft.Bank.Setup · BC23-30 · source at ea08af5e · facts from BC29

Properties

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.

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.” 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.” 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.” 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.” 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” (source table)
• Page 1061 “Select Payment Service” (source table)
• Page 1062 “Select Payment Service Type” (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” (6 calls: CanChangePaymentService → FindFieldByName, CanChangePaymentService → GetRecordRef, CreateReportingArgs → FindFieldByName, …)
• Codeunit 8400 “Record Set Management” (4 calls: GetDefaultPaymentServices → GetSet, GetDefaultPaymentServices → SaveSet, LoadSet → GetSet, …)
• Page 1060 “Payment Services” (1 call: AskUserToSetupNewPaymentService → (object))
• Page 1061 “Select Payment Service” (1 call: SelectPaymentService → (object))
• Page 1062 “Select Payment Service Type” (1 call: NewPaymentService → (object))

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.