# Accept Payment Accept a Payment. On acceptance, payment instructions will be returned (if source = counterparty) or funds will begin processing (if source = account). Endpoint: POST /v1/payments/{payment_id}/accept Version: 1.1.2 Security: OAuth2Flow ## Path parameters: - `id` (string, required) Payment ID ## Header parameters: - `Authorization` (string) OAuth bearer token (see authentication flows) - `x-l2f-request-id` (string) Optional Unique ID per request, useful for fault resolution/diagnosis and audit. - `x-l2f-idempotency-id` (string) Unique ID used to safely retry an operation. See idempotency section for more details. ## Response 200 fields (application/json): - `data` (object, required) - `data.id` (string, required) Unique ID of the payment, to be used to lookup payment details and status - `data.status` (string) Status of the payment * REQUESTED - Payment request is created and has passed validation. It must be accepted before it can be used * ACCEPTED - Payment request has been accepted and is waiting execution. At this point it cannot be cancelled. * INPROGRESS - Payment is in progress. * EXECUTED - Payment Processing have been completed. * FAILURE - There is a problem or failure with the payment. View payment details for more information. Enum: "ACCEPTED" ## Response 400 fields (application/json): - `errors` (array) Error List - `errors.code` (string) Layer2 Standard Error Code - `errors.description` (string) Error Description ## Response 401 fields (application/json): - `errors` (array) Error List - `errors.code` (string) Layer2 Standard Error Code - `errors.description` (string) Error Description ## Response 404 fields (application/json): - `errors` (array) Error List - `errors.code` (string) Layer2 Standard Error Code - `errors.description` (string) Error Description ## Response 500 fields (application/json): - `errors` (array) Error List - `errors.code` (string) Layer2 Standard Error Code - `errors.description` (string) Error Description