---
title: "Create org acceptance configuration"
method: POST
path: "/payment-methods-configs/v1/acceptances/processing-codes/{processingCode}"
tags: ["Payment method acceptances"]
---

# Create org acceptance configuration

`POST /payment-methods-configs/v1/acceptances/processing-codes/{processingCode}`

Create acceptance configuration for a processing code operation on the organization level. This level can be used as a default configuration for all programs and accounts in this org. There is always only one configuration by operation by org. New creation attempts for the same operation receive a conflict response.

**Note:** This is a PCI endpoint, use the https://gw-pci.pismolabs.io environment.

## Request body

- CreateAcceptanceRequest — Create an acceptance configuration record
  - `authorization` AuthorizationAcceptanceConfig — Group of acceptances related to the authorization flow.
    - `external_calculation_endpoint` string — Endpoint that is called when there is an external integration to simulate and calculate purchases.
    - `cancellation_threshold` integer — Time in minutes this operation should be canceled after being approved and not receiving any confirmation.
    - `confirmation_verification_endpoint` string — Endpoint that is called to verify whether an authorization was confirmed or not. If this endpoint is not configured, no external verification is made and a direct confirmation call should be performed on the payment methods endpoint.
    - `confirmation_verification_mtls` boolean — Should the confirmation verification endpoint be called using mTLS? This can only be `true` if `confirmation_verification_endpoint` and `confirmation_verification_mtls_prefix` are passed. Default is `false`.
    - `confirmation_verification_mtls_prefix` string — Prefix to be used when the verification endpoint is called using mTLS. This prefix is appended to the host configured in the confirmation verification endpoint when using mTLS. The prefix can be set and is **REQUIRED** only if `confirmation_verification_mtls` is `true` and the `confirmation_verification_endpoint` is configured.
    - `confirmation_verification_rate` integer — Time in minutes the platform should call external endpoint to verify whether the authorization was captured and confirmed or not. If this field is present, the verification endpoint is required to be configured. This verification happens until either the authorization is confirmed or the cancel after N minutes threshold is reached.
    - `require_external_authentication` boolean — Does this org/program/account require a call to an external authentication entity? Default is `false`.
    - `update_balance_after_discharge` boolean — If set to `true`, the platform will update the account balances only after the discharge process is completed. By default, this value is `false`, and the platform updates the account balances during the authorization process. This field applies to credit authorizations only.
    - `rules` Rules — Validation rules performed in the payment methods flow.
  - `payment` PaymentAcceptanceConfig — Group of acceptances related to the payments flow.
    - `retroactive_payment_time_restriction` integer — The number of days allowed for this operation be backdated.
    - `require_external_authentication` boolean — Does this org/program/account require a call to an external authentication entity? Default is `false`.
    - `update_balance_after_discharge` boolean — If set to `true`, the platform will update the account balances only after the discharge process is completed. By default, this value is `false`, and the platform updates the account balances during the authorization process. This field applies to credit authorizations only.
    - `rules` Rules — Validation rules performed in the payment methods flow.
  - `transfer` TransferAcceptanceConfig — Group of acceptances related to the transfer flow.
    - `from` object — Group of acceptances related to the source account.
      - `retroactive_payment_time_restriction` integer — The number of days allowed for this operation be backdated.
      - `require_external_authentication` boolean — Does this org/program/account require a call to an external authentication entity? Default is `false`.
      - `rules` Rules — Validation rules performed in the payment methods flow.
    - `to` object — Group of acceptances related to the target account.
      - `retroactive_payment_time_restriction` integer — The number of days allowed for this operation be backdated.
      - `require_external_authentication` boolean — Does this org/program/account require a call to an external authentication entity? Default is `false`.
      - `rules` Rules — Validation rules performed in the payment methods flow.

## Response `201`

Created

- CreateAcceptanceResponse — Create acceptance configuration record response
  - `authorization` AuthorizationAcceptanceConfig — Group of acceptances related to the authorization flow.
    - `external_calculation_endpoint` string — Endpoint that is called when there is an external integration to simulate and calculate purchases.
    - `cancellation_threshold` integer — Time in minutes this operation should be canceled after being approved and not receiving any confirmation.
    - `confirmation_verification_endpoint` string — Endpoint that is called to verify whether an authorization was confirmed or not. If this endpoint is not configured, no external verification is made and a direct confirmation call should be performed on the payment methods endpoint.
    - `confirmation_verification_mtls` boolean — Should the confirmation verification endpoint be called using mTLS? This can only be `true` if `confirmation_verification_endpoint` and `confirmation_verification_mtls_prefix` are passed. Default is `false`.
    - `confirmation_verification_mtls_prefix` string — Prefix to be used when the verification endpoint is called using mTLS. This prefix is appended to the host configured in the confirmation verification endpoint when using mTLS. The prefix can be set and is **REQUIRED** only if `confirmation_verification_mtls` is `true` and the `confirmation_verification_endpoint` is configured.
    - `confirmation_verification_rate` integer — Time in minutes the platform should call external endpoint to verify whether the authorization was captured and confirmed or not. If this field is present, the verification endpoint is required to be configured. This verification happens until either the authorization is confirmed or the cancel after N minutes threshold is reached.
    - `require_external_authentication` boolean — Does this org/program/account require a call to an external authentication entity? Default is `false`.
    - `update_balance_after_discharge` boolean — If set to `true`, the platform will update the account balances only after the discharge process is completed. By default, this value is `false`, and the platform updates the account balances during the authorization process. This field applies to credit authorizations only.
    - `rules` Rules — Validation rules performed in the payment methods flow.
  - `payment` PaymentAcceptanceConfig — Group of acceptances related to the payments flow.
    - `retroactive_payment_time_restriction` integer — The number of days allowed for this operation be backdated.
    - `require_external_authentication` boolean — Does this org/program/account require a call to an external authentication entity? Default is `false`.
    - `update_balance_after_discharge` boolean — If set to `true`, the platform will update the account balances only after the discharge process is completed. By default, this value is `false`, and the platform updates the account balances during the authorization process. This field applies to credit authorizations only.
    - `rules` Rules — Validation rules performed in the payment methods flow.
  - `transfer` TransferAcceptanceConfig — Group of acceptances related to the transfer flow.
    - `from` object — Group of acceptances related to the source account.
      - `retroactive_payment_time_restriction` integer — The number of days allowed for this operation be backdated.
      - `require_external_authentication` boolean — Does this org/program/account require a call to an external authentication entity? Default is `false`.
      - `rules` Rules — Validation rules performed in the payment methods flow.
    - `to` object — Group of acceptances related to the target account.
      - `retroactive_payment_time_restriction` integer — The number of days allowed for this operation be backdated.
      - `require_external_authentication` boolean — Does this org/program/account require a call to an external authentication entity? Default is `false`.
      - `rules` Rules — Validation rules performed in the payment methods flow.

## Other responses

- `400` — Bad request
- `401` — Access token is missing or invalid
- `403` — The request has been lost
- `409` — The specified resource status conflicts with the current request.
- `500` — Internal server error

---

[API](https://skmtc.net/pismo/apis/platform-authentication.md) · [All operations](https://skmtc.net/pismo/apis/platform-authentication/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pismo/platform-authentication/revisions/935b62e16de4/schema)