# GET /api/merchants/{id}/billing/payment-method/capture-readiness

Payment Methods: Reports whether capture is configured.

Answers whether the reseller-level prerequisites for capturing a stored method are in place:
whether the reseller has a collection merchant and a card-capture HPP configured and which
instrument kinds are allowed, plus the parent reseller id. Backs the operator UI's load-time
pre-flight; the authoritative checks still run server-side on capture initiation.

**Operation ID:** `merchantBillingPaymentMethodGetCaptureReadiness`

## Authorization

Requires: MerchantBilling.PaymentMethods, MerchantBilling.PaymentMethods.Manage, merchant scope.

Required permissions:
- `MerchantBilling.PaymentMethods`
- `MerchantBilling.PaymentMethods.Manage`

## Parameters

| Name | In | Required | Type | Description |
| --- | --- | --- | --- | --- |
| id | path | yes | string(uuid) | The billed merchant whose capture readiness is requested. |
| suppressNulls | query | no | boolean | If true, omit properties with null values. |

## Responses

### 200

OK

**Content type:** `application/json`

Schema: `MerchantBillingPaymentMethodCaptureReadinessDto`

Properties:
- `resellerId` (string(uuid)): The merchant's parent reseller, so the page can deep-link to the reseller's billing preferences  (`/reseller/{ResellerId}`) where the operator fixes any unmet prerequisite. The caller is  already authorized for the merchant, so this is the caller's own reseller (no cross-reseller leak).
- `collectionMerchantConfigured` (boolean): Whether the reseller has a `CollectionMerchantId` configured (required for any capture).
- `captureHppConfigured` (boolean): Whether the reseller has a card-capture `CaptureHppPageId` configured (required for any capture).
- `cardAllowed` (boolean): Whether the reseller's allowlist permits Card capture (`AllowCardPayments != false`).
- `achAllowed` (boolean): Whether the reseller's allowlist permits ACH capture (`AllowAchPayments != false`).
- `effectiveResellerId` (string(uuid)): The reseller whose collection configuration the flags above describe. Equal to  `resellerId` when the merchant's reseller has its own configuration (or nothing is  configured anywhere); the nearest configured ancestor when the configuration is inherited.  Absent from responses produced before inheritance existed.
- `effectiveResellerName` (string): The display name of `effectiveResellerId`, when it resolved.
- `isInherited` (boolean): Whether the configuration is inherited from an ancestor of the merchant's reseller rather than  set on it. When `true`, an unmet prerequisite is fixed on  `effectiveResellerId`, not on `resellerId`.
- `effectiveResellerWithinScope` (boolean): Whether the calling operator may act on `effectiveResellerId`. Always  `true` when the configuration is not inherited (the caller is already authorized  for the merchant's reseller); for an inherited configuration it is `false` for  an operator whose own reseller sits below the configured ancestor, who must ask the  administrator or that ancestor to change it.

### 403

Forbidden

**Content type:** `application/json`

Schema: `RemoteServiceErrorResponse`

Properties:
- `error` (RemoteServiceErrorInfo)

### 401

Unauthorized

**Content type:** `application/json`

Schema: `RemoteServiceErrorResponse`

Properties:
- `error` (RemoteServiceErrorInfo)

### 400

Bad Request

**Content type:** `application/json`

Schema: `RemoteServiceErrorResponse`

Properties:
- `error` (RemoteServiceErrorInfo)

### 404

Not Found

**Content type:** `application/json`

Schema: `RemoteServiceErrorResponse`

Properties:
- `error` (RemoteServiceErrorInfo)

### 501

Not Implemented

**Content type:** `application/json`

Schema: `RemoteServiceErrorResponse`

Properties:
- `error` (RemoteServiceErrorInfo)

### 500

Internal Server Error

**Content type:** `application/json`

Schema: `RemoteServiceErrorResponse`

Properties:
- `error` (RemoteServiceErrorInfo)

### default

The request failed. The body carries the standard error envelope: a machine-readable `error.code`, a human-readable `error.message`, and `error.validationErrors` when the failure was a validation rejection. See the error-code reference in this document's description for the values `error.code` can take.

**Content type:** `application/json`

Schema: `RemoteServiceErrorResponse`

Properties:
- `error` (RemoteServiceErrorInfo)

### 429

The request was refused because a rate limit was exceeded, or because something a later retry can clear stopped it. A rate limit refusal carries an `application/problem+json` body: wait at least the interval `Retry-After` names before retrying, then back off. Limits are tuned per deployment, so read the allowance from the response headers rather than assuming a fixed ceiling. Any other refusal carries the standard error envelope as `application/json`, and its `error.code` names the cause.

**Content type:** `application/problem+json`

Schema: `RateLimitProblemDetails`

Properties:
- `type` (string) required: The problem type identifier. Always the same value: the failure is the status code itself,  so there is no sub-type for a caller to branch on.
- `title` (string) required: A short, human-readable summary of the problem type.
- `status` (integer(int32)) required: The HTTP status code, repeated in the body as the problem-details format defines.
- `detail` (string) required: A human-readable explanation of this occurrence of the problem.
- `retryAfterSeconds` (integer(int32)) required: How long to wait before retrying, in whole seconds, carrying the same figure as the  `Retry-After` header. Always at least one: a value of zero would invite an immediate  retry that is certain to be rejected again.

**Content type:** `application/json`

Schema: `RemoteServiceErrorResponse`

Properties:
- `error` (RemoteServiceErrorInfo)

## Example request

Every block below sends the same request. Replace {{BASE_URL}} with the address of the API you are calling and {{API_KEY}} with your own key.

### cURL

```bash
curl -X GET "{{BASE_URL}}/api/merchants/{id}/billing/payment-method/capture-readiness" \
  -H "api-key: {{API_KEY}}"
```

### PowerShell

```powershell
$headers = @{
    'api-key' = '{{API_KEY}}'
}

$response = Invoke-RestMethod -Method GET -Uri '{{BASE_URL}}/api/merchants/{id}/billing/payment-method/capture-readiness' `
    -Headers $headers
```

### TypeScript (SDK)

```bash
npm install @winkpg/winkpg-api
```

```typescript
import { Configuration, MerchantBillingApi } from '@winkpg/winkpg-api';

const api = new MerchantBillingApi(new Configuration({
  basePath: '{{BASE_URL}}',
  apiKey: '{{API_KEY}}',
}));

const { data } = await api.merchantBillingPaymentMethodGetCaptureReadiness("3fa85f64-5717-4562-b3fc-2c963f66afa6");
```

### TypeScript (raw HTTP)

```typescript
const response = await fetch('{{BASE_URL}}/api/merchants/{id}/billing/payment-method/capture-readiness', {
  method: 'GET',
  headers: {
    "api-key": "{{API_KEY}}",
  },
});

const data = await response.json();
```

### C# (SDK)

```bash
dotnet add package WinkPg.Api.Client
```

```csharp
using WinkPg.Api.Client.Api;
using WinkPg.Api.Client.Client;

var config = new Configuration { BasePath = "{{BASE_URL}}" };
config.AddApiKey("api-key", "{{API_KEY}}");

var api = new MerchantBillingApi(config);
var result = await api.MerchantBillingPaymentMethodGetCaptureReadinessAsync(Guid.Parse("3fa85f64-5717-4562-b3fc-2c963f66afa6"));
```

### C# (raw HTTP)

```csharp
using var http = new HttpClient { BaseAddress = new Uri("{{BASE_URL}}") };

var request = new HttpRequestMessage(new HttpMethod("GET"), "/api/merchants/{id}/billing/payment-method/capture-readiness");
request.Headers.Add("api-key", "{{API_KEY}}");

var response = await http.SendAsync(request);
response.EnsureSuccessStatusCode();
var json = await response.Content.ReadAsStringAsync();
```

### Python (SDK)

```bash
pip install winkpg-api
```

```python
import winkpg_api

configuration = winkpg_api.Configuration(host="{{BASE_URL}}")
configuration.api_key["ApiKey"] = "{{API_KEY}}"

with winkpg_api.ApiClient(configuration) as client:
    api = winkpg_api.MerchantBillingApi(client)
    result = api.merchant_billing_payment_method_get_capture_readiness("3fa85f64-5717-4562-b3fc-2c963f66afa6")
```

### Python (raw HTTP)

```bash
pip install requests
```

```python
import requests

headers = {
    "api-key": "{{API_KEY}}",
}

response = requests.request(
    "GET",
    "{{BASE_URL}}/api/merchants/{id}/billing/payment-method/capture-readiness",
    headers=headers,
)
response.raise_for_status()
data = response.json()
```

## See also

- [All documentation](https://devportal-simpay-sbx.winkpg.io/llms.txt): the machine-readable index of every public page on this site.