Looking for ePay classic docs? Go to docs.epay.dk
ePay documentationDocsePay documentation
Payment Methods

Disable Stored Payment Method

OpenAPI Spec

Test this endpoint live

Open the same request directly in API Explorer.

Open in API Explorer

Server URL

DELETE
/public/api/v1/payment-methods/{id}

Permanently disables a stored payment method for the authenticated customer. The payment method is immediately removed from the payment window and can no longer be used for quick checkout without entering card information.

This operation is irreversible and idempotent. It returns 200 OK with no response body even when the payment method is not currently stored; in that case, no action is taken.

Authorization

BearerAuth
AuthorizationBearer <token>

In: header

Path Parameters

idstring
Required

The ID of the payment method.

Format:
uuid

Response Body

application/json

application/json

application/json

curl -X DELETE "https://example.com/public/api/v1/payment-methods/01924756-d1f6-738d-8040-90d76cedf01f"
Empty
{  "errorCode": "SERVER_ERROR",  "message": "An unexpected system error"}
{  "errorCode": "VALIDATION_ERROR",  "message": "Input validation errors",  "errors": {    "amount": [      "[required]: Is a required non-nullable field",      "[int]: Must be an integer",      "[min:0]: Must be greater than 0",      "[max:999999999]: Must be less than 999999999"    ]  }}
{  "errorCode": "SERVER_ERROR",  "message": "An unexpected system error"}

List Imported Payment Methods

Retrieve imported payment methods for the authenticated merchant using cursor-based pagination ordered by newest id. Each entry includes the imported payment method, its underlying payment method, and associated card details (if any).

List Webhooks

Returns a paginated list of active webhooks configured for the authenticated merchant. Use this endpoint to audit webhook destinations, verify subscribed events, and ensure each webhook aligns with your point-of-sale domains. Webhooks are not required Webhooks are separate from the main payment flow and act as a general event notification system. You should use them only if you need to track changes to your ePay data in a system that is different from the one initiating the request. For all payment-related operations, you should use the notificationUrl provided in each request. This is the primary mechanism for receiving the outcome of a payment or operation.