--- title: "Create authorization configuration by program" method: POST path: "/v1/config/program/{programId}" tags: ["Authorization configurations"] --- # Create authorization configuration by program `POST /v1/config/program/{programId}` Create the authorization configuration at the program level. This level can be used as a default configuration for all accounts in this program and at a more granular level than org. A program can only have one configuration. Executing this endpoint on a program that already has a configuration defined for it generates a conflict response. ## Path parameters - `programId` integer, required ## Headers - `x-tenant` string, required ## Request body - CreateNetworkTransactionsConfigRequest — Collection of options that can be customized by organization, program, account, and BIN. - `use_anti_fraud_response_code` boolean — Flag indicates whether we should use the response code sent in anti-fraud. - `zero_balance_url` string — Indicates that it’s a Zero Balance flow, so the URL to call the customer’s service is informed. **NOTE:** This is only required for Zero balance. - `should_use_anti_fraud_decision` boolean — Flag indicates whether anti-fraud decisions should be used. - `approve_anti_fraud_unavailable` boolean — If set to `true` when anti-fraud is unavailable, the anti-fraud check is marked as `APPROVED`. If set to `false`, it is marked as `REJECTED`. - `enabled_partial_authorization` boolean — By default, authorizations don’t validate partial authorization, but if this property is enabled, it allows the platform to process partial authorizations for a given org/program/account. **NOTE:** This property also depends on the merchant, as it is necessary for the merchant to be able to partially authorize. - `disable_dcc` boolean — This setting indicates whether or not the program allows dynamic currency conversion (DCC) transactions. By default, every program allows DCC transactions. In case it's necessary to block this type of transaction, the configuration must be set to `true`. - `deny_all_authorizations` boolean — Flag indicates whether authorizations should be denied. This is useful for cases where a product is deprecated or during a migration process. - `use_settlement_from_network` boolean — By default, in clearing flow for international purchases, the authorizations use the same settlement amount of authorization (online flow). Setting this flag to truemeans the system will use the settlement amount from the clearing message, which can be different from authorization. - `use_rates_fee_models` boolean — Flag indicates whether rate fee models should be used. - `call_anti_fraud_when_cancelling` boolean — Flag indicates whether the anti-fraud API should be called during cancellation. - `days_to_cancel_pre_authorization` integer — Number of days to cancel pre-authorization. **NOTE:** The minimum number of days is 1 and the maximum is 60. - `days_to_cancel_authorization` integer — Number of days to cancel authorization. **NOTE:** The minimum number of days is 1 and the maximum is 60. - `days_to_cancel_pre_authorization_migration` integer — Number of days to cancel migrated pre-authorization. **NOTE:** The minimum number of days is 1 and the maximum is 60. - `days_to_cancel_authorization_migration` integer — Number of days to cancel migrated authorization. **NOTE:** The minimum number of days is 1 and the maximum is 60. - `always_call_ledger_rules` boolean — Flag indicates whether Ledger API and Rules API should be always called, even when the authorization has already been denied. ## Response `201` Created - CreateNetworkTransactionsConfigResponse — Collection of options that can be customized by organization, program, account, and BIN. - `use_anti_fraud_response_code` boolean — Flag indicates whether we should use the response code sent in anti-fraud. - `zero_balance_url` string — Indicates that it’s a Zero Balance flow, so the URL to call the customer’s service is informed. **NOTE:** This is only required for Zero balance. - `should_use_anti_fraud_decision` boolean — Flag indicates whether anti-fraud decisions should be used. - `approve_anti_fraud_unavailable` boolean — If set to `true` when anti-fraud is unavailable, the anti-fraud check is marked as `APPROVED`. If set to `false`, it is marked as `REJECTED`. - `enabled_partial_authorization` boolean — By default, authorizations don’t validate partial authorization, but if this property is enabled, it allows the platform to process partial authorizations for a given org/program/account. **NOTE:** This property also depends on the merchant, as it is necessary for the merchant to be able to partially authorize. - `disable_dcc` boolean — This setting indicates whether or not the program allows dynamic currency conversion (DCC) transactions. By default, every program allows DCC transactions. In case it's necessary to block this type of transaction, the configuration must be set to `true`. - `deny_all_authorizations` boolean — Flag indicates whether authorizations should be denied. This is useful for cases where a product is deprecated or during a migration process. - `use_settlement_from_network` boolean — By default, in clearing flow for international purchases, the authorizations use the same settlement amount of authorization (online flow). Setting this flag to truemeans the system will use the settlement amount from the clearing message, which can be different from authorization. - `use_rates_fee_models` boolean — Flag indicates whether rate fee models should be used. - `call_anti_fraud_when_cancelling` boolean — Flag indicates whether the anti-fraud API should be called during cancellation. - `days_to_cancel_pre_authorization` integer — Number of days to cancel pre-authorization. **NOTE:** The minimum number of days is 1 and the maximum is 60. - `days_to_cancel_authorization` integer — Number of days to cancel authorization. **NOTE:** The minimum number of days is 1 and the maximum is 60. - `days_to_cancel_pre_authorization_migration` integer — Number of days to cancel migrated pre-authorization. **NOTE:** The minimum number of days is 1 and the maximum is 60. - `days_to_cancel_authorization_migration` integer — Number of days to cancel migrated authorization. **NOTE:** The minimum number of days is 1 and the maximum is 60. - `always_call_ledger_rules` boolean — Flag indicates whether Ledger API and Rules API should be always called, even when the authorization has already been denied. ## 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/versions/935b62e16de4/schema)