Antylogic
DemoApp login

399 operational guides

Docs sections
DocsTPV
Device

Delete a TPV Payment Method

Permanently remove one TPV payment method from the active Harbor Soho configuration. The action starts in TPV Settings, on the Payment methods tab, and requires `tpv:manage`.

In this article

Use this guide when a payment option should no longer be available to operators in the TPV for the selected location. In the GB documentation runtime, the example context is Harbor Demo Group > Harbor Soho.

Deletion removes the payment method row instead of marking it inactive. Antylogic asks for confirmation first, then refreshes the Payment methods list and TPV settings so related quick-payment references can update.

Before you start

  • The operator is signed in to Harbor Demo Group with Harbor Soho selected as the active location.
  • A payment method exists in the selected location.
  • The operator has the location permission `tpv:manage`; `tpv:view` can load the list but cannot delete records.
  • For documentation captures, create or select a disposable method named by `TPV_PAYMENT_METHOD_DELETE_NAME`. Do not delete the seeded `TPV_PAYMENT_METHOD_ID`, because other TPV flows may depend on it.

Instructions

  1. 1.

    Open Payment methods

    Open `${APP_DEEPLINK_BASE}${ORG_ID}/${LOCATION_ID}/location/tpv?tab=payment-methods` and wait for TPV Settings to load the Payment methods tab for Harbor Soho. Current captures may still show Spanish fallback labels such as `Metodos de pago` and `Nuevo metodo`.

  2. 2.

    Choose the method to remove

    Find the disposable payment method row for the current location. Only remove a method that is no longer needed, because the delete is permanent.

  3. 3.

    Start the deletion

    Open the row actions and choose Delete. If the operator does not have `tpv:manage`, the table does not expose the Delete action and a direct API call is rejected by the backend.

  4. 4.

    Review the confirmation

    The `Eliminar recurso` confirmation modal shows the selected payment method name. Choose Cancel to keep the method, or continue with the destructive Delete action. There is no typed-name confirmation.

  5. 5.

    Confirm deletion

    Select Delete in the modal. The app sends `DELETE /api/app/{orgId}/{locationId}/tpv-payment-methods/{id}` using the selected id from the route and no request payload.

  6. 6.

    Verify the refreshed list

    After a successful `204 NoContent` response, the modal closes, the Payment methods list reloads, and the removed method should no longer appear. Review quick-payment settings if the method was used as a primary or secondary quick payment option.

Validations and limits

  • `tpv:manage` is required to expose and execute deletion; `tpv:view` alone is read-only for this action.
  • The delete endpoint uses only the `{id}` path segment and does not consume a request body.
  • The id must be non-empty after trimming, and the request must have a location context.
  • The payment method must exist and belong to the active location; ids from another location are treated as not found.
  • A successful delete returns `204 NoContent`.
  • The delete is physical: there is no soft delete, inactive-state fallback, bulk delete endpoint, or typed-name confirmation.
  • Deleting a method can clear quick-payment references and may affect historical payment links, so production operators should confirm downstream impact before removing a method used by tickets or payment operations.

Expected result

The selected TPV payment method is physically removed from Harbor Soho, the Payment methods list refreshes, and related TPV settings are invalidated so quick-payment references reflect the updated configuration.

Related articles