Info: This ns is auto-generated from the Stripe OpenAPI spec.
Info: This ns is auto-generated from the Stripe OpenAPI spec.
(create-cardholders {:keys [body]})Create a cardholder
HTTP Method: POST Endpoint: /v1/issuing/cardholders
Example Usage: (create-cardholders {})
Create a cardholder
HTTP Method: POST
Endpoint: /v1/issuing/cardholders
Example Usage:
(create-cardholders {})(create-cards {:keys [body]})Create a card
HTTP Method: POST Endpoint: /v1/issuing/cards
Example Usage: (create-cards {})
Create a card
HTTP Method: POST
Endpoint: /v1/issuing/cards
Example Usage:
(create-cards {})(create-disputes {:keys [body]})Create a dispute
HTTP Method: POST Endpoint: /v1/issuing/disputes
Example Usage: (create-disputes {})
Create a dispute
HTTP Method: POST
Endpoint: /v1/issuing/disputes
Example Usage:
(create-disputes {})(create-personalization-designs {:keys [body]})Create a personalization design
HTTP Method: POST Endpoint: /v1/issuing/personalization_designs
Example Usage: (create-personalization-designs {})
Create a personalization design
HTTP Method: POST
Endpoint: /v1/issuing/personalization_designs
Example Usage:
(create-personalization-designs {})(list-all-authorizations {:keys [query-params]})List all authorizations
HTTP Method: GET Endpoint: /v1/issuing/authorizations
Query Parameters:
ending_before is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, starting with obj_bar, your subsequent call can include ending_before=obj_bar in order to fetch the previous page of the list.starting_after is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, ending with obj_foo, your subsequent call can include starting_after=obj_foo in order to fetch the next page of the list.pending, closed, or reversed.Example Usage: (list-all-authorizations {:query-params {:limit 10}})
List all authorizations
HTTP Method: GET
Endpoint: /v1/issuing/authorizations
Query Parameters:
- card (String): Only return authorizations that belong to the given card.
- cardholder (String): Only return authorizations that belong to the given cardholder.
- created (Unknown): Only return authorizations that were created during the given date interval.
- ending-before (String): A cursor for use in pagination. `ending_before` is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, starting with `obj_bar`, your subsequent call can include `ending_before=obj_bar` in order to fetch the previous page of the list.
- expand (Array): Specifies which fields in the response should be expanded.
- limit (Integer): A limit on the number of objects to be returned. Limit can range between 1 and 100, and the default is 10.
- starting-after (String): A cursor for use in pagination. `starting_after` is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, ending with `obj_foo`, your subsequent call can include `starting_after=obj_foo` in order to fetch the next page of the list.
- status (String): Only return authorizations with the given status. One of `pending`, `closed`, or `reversed`.
Example Usage:
(list-all-authorizations {:query-params {:limit 10}})(list-all-cardholders {:keys [query-params]})List all cardholders
HTTP Method: GET Endpoint: /v1/issuing/cardholders
Query Parameters:
ending_before is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, starting with obj_bar, your subsequent call can include ending_before=obj_bar in order to fetch the previous page of the list.starting_after is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, ending with obj_foo, your subsequent call can include starting_after=obj_foo in order to fetch the next page of the list.active, inactive, or blocked.individual or company.Example Usage: (list-all-cardholders {:query-params {:limit 10}})
List all cardholders
HTTP Method: GET
Endpoint: /v1/issuing/cardholders
Query Parameters:
- created (Unknown): Only return cardholders that were created during the given date interval.
- email (String): Only return cardholders that have the given email address.
- ending-before (String): A cursor for use in pagination. `ending_before` is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, starting with `obj_bar`, your subsequent call can include `ending_before=obj_bar` in order to fetch the previous page of the list.
- expand (Array): Specifies which fields in the response should be expanded.
- limit (Integer): A limit on the number of objects to be returned. Limit can range between 1 and 100, and the default is 10.
- phone-number (String): Only return cardholders that have the given phone number.
- starting-after (String): A cursor for use in pagination. `starting_after` is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, ending with `obj_foo`, your subsequent call can include `starting_after=obj_foo` in order to fetch the next page of the list.
- status (String): Only return cardholders that have the given status. One of `active`, `inactive`, or `blocked`.
- type (String): Only return cardholders that have the given type. One of `individual` or `company`.
Example Usage:
(list-all-cardholders {:query-params {:limit 10}})(list-all-cards {:keys [query-params]})List all cards
HTTP Method: GET Endpoint: /v1/issuing/cards
Query Parameters:
ending_before is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, starting with obj_bar, your subsequent call can include ending_before=obj_bar in order to fetch the previous page of the list.starting_after is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, ending with obj_foo, your subsequent call can include starting_after=obj_foo in order to fetch the next page of the list.active, inactive, or canceled.virtual or physical.Example Usage: (list-all-cards {:query-params {:limit 10}})
List all cards
HTTP Method: GET
Endpoint: /v1/issuing/cards
Query Parameters:
- cardholder (String): Only return cards belonging to the Cardholder with the provided ID.
- created (Unknown): Only return cards that were issued during the given date interval.
- ending-before (String): A cursor for use in pagination. `ending_before` is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, starting with `obj_bar`, your subsequent call can include `ending_before=obj_bar` in order to fetch the previous page of the list.
- exp-month (Integer): Only return cards that have the given expiration month.
- exp-year (Integer): Only return cards that have the given expiration year.
- expand (Array): Specifies which fields in the response should be expanded.
- last4 (String): Only return cards that have the given last four digits.
- limit (Integer): A limit on the number of objects to be returned. Limit can range between 1 and 100, and the default is 10.
- personalization-design (String): The personalization-design parameter.
- starting-after (String): A cursor for use in pagination. `starting_after` is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, ending with `obj_foo`, your subsequent call can include `starting_after=obj_foo` in order to fetch the next page of the list.
- status (String): Only return cards that have the given status. One of `active`, `inactive`, or `canceled`.
- type (String): Only return cards that have the given type. One of `virtual` or `physical`.
Example Usage:
(list-all-cards {:query-params {:limit 10}})(list-all-disputes {:keys [query-params]})List all disputes
HTTP Method: GET Endpoint: /v1/issuing/disputes
Query Parameters:
ending_before is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, starting with obj_bar, your subsequent call can include ending_before=obj_bar in order to fetch the previous page of the list.starting_after is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, ending with obj_foo, your subsequent call can include starting_after=obj_foo in order to fetch the next page of the list.Example Usage: (list-all-disputes {:query-params {:limit 10}})
List all disputes
HTTP Method: GET
Endpoint: /v1/issuing/disputes
Query Parameters:
- created (Unknown): Only return Issuing disputes that were created during the given date interval.
- ending-before (String): A cursor for use in pagination. `ending_before` is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, starting with `obj_bar`, your subsequent call can include `ending_before=obj_bar` in order to fetch the previous page of the list.
- expand (Array): Specifies which fields in the response should be expanded.
- limit (Integer): A limit on the number of objects to be returned. Limit can range between 1 and 100, and the default is 10.
- starting-after (String): A cursor for use in pagination. `starting_after` is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, ending with `obj_foo`, your subsequent call can include `starting_after=obj_foo` in order to fetch the next page of the list.
- status (String): Select Issuing disputes with the given status.
- transaction (String): Select the Issuing dispute for the given transaction.
Example Usage:
(list-all-disputes {:query-params {:limit 10}})(list-all-personalization-designs {:keys [query-params]})List all personalization designs
HTTP Method: GET Endpoint: /v1/issuing/personalization_designs
Query Parameters:
ending_before is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, starting with obj_bar, your subsequent call can include ending_before=obj_bar in order to fetch the previous page of the list.starting_after is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, ending with obj_foo, your subsequent call can include starting_after=obj_foo in order to fetch the next page of the list.Example Usage: (list-all-personalization-designs {:query-params {:limit 10}})
List all personalization designs
HTTP Method: GET
Endpoint: /v1/issuing/personalization_designs
Query Parameters:
- ending-before (String): A cursor for use in pagination. `ending_before` is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, starting with `obj_bar`, your subsequent call can include `ending_before=obj_bar` in order to fetch the previous page of the list.
- expand (Array): Specifies which fields in the response should be expanded.
- limit (Integer): A limit on the number of objects to be returned. Limit can range between 1 and 100, and the default is 10.
- lookup-keys (Array): Only return personalization designs with the given lookup keys.
- preferences (Object): Only return personalization designs with the given preferences.
- starting-after (String): A cursor for use in pagination. `starting_after` is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, ending with `obj_foo`, your subsequent call can include `starting_after=obj_foo` in order to fetch the next page of the list.
- status (String): Only return personalization designs with the given status.
Example Usage:
(list-all-personalization-designs {:query-params {:limit 10}})(list-all-physical-bundles {:keys [query-params]})List all physical bundles
HTTP Method: GET Endpoint: /v1/issuing/physical_bundles
Query Parameters:
ending_before is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, starting with obj_bar, your subsequent call can include ending_before=obj_bar in order to fetch the previous page of the list.starting_after is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, ending with obj_foo, your subsequent call can include starting_after=obj_foo in order to fetch the next page of the list.Example Usage: (list-all-physical-bundles {:query-params {:limit 10}})
List all physical bundles
HTTP Method: GET
Endpoint: /v1/issuing/physical_bundles
Query Parameters:
- ending-before (String): A cursor for use in pagination. `ending_before` is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, starting with `obj_bar`, your subsequent call can include `ending_before=obj_bar` in order to fetch the previous page of the list.
- expand (Array): Specifies which fields in the response should be expanded.
- limit (Integer): A limit on the number of objects to be returned. Limit can range between 1 and 100, and the default is 10.
- starting-after (String): A cursor for use in pagination. `starting_after` is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, ending with `obj_foo`, your subsequent call can include `starting_after=obj_foo` in order to fetch the next page of the list.
- status (String): Only return physical bundles with the given status.
- type (String): Only return physical bundles with the given type.
Example Usage:
(list-all-physical-bundles {:query-params {:limit 10}})(list-all-tokens {:keys [query-params]})List all issuing tokens for card
HTTP Method: GET Endpoint: /v1/issuing/tokens
Query Parameters:
ending_before is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, starting with obj_bar, your subsequent call can include ending_before=obj_bar in order to fetch the previous page of the list.starting_after is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, ending with obj_foo, your subsequent call can include starting_after=obj_foo in order to fetch the next page of the list.Example Usage: (list-all-tokens {:query-params {:limit 10}})
List all issuing tokens for card
HTTP Method: GET
Endpoint: /v1/issuing/tokens
Query Parameters:
- card (String): The Issuing card identifier to list tokens for. (required)
- created (Unknown): Only return Issuing tokens that were created during the given date interval.
- ending-before (String): A cursor for use in pagination. `ending_before` is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, starting with `obj_bar`, your subsequent call can include `ending_before=obj_bar` in order to fetch the previous page of the list.
- expand (Array): Specifies which fields in the response should be expanded.
- limit (Integer): A limit on the number of objects to be returned. Limit can range between 1 and 100, and the default is 10.
- starting-after (String): A cursor for use in pagination. `starting_after` is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, ending with `obj_foo`, your subsequent call can include `starting_after=obj_foo` in order to fetch the next page of the list.
- status (String): Select Issuing tokens with the given status.
Example Usage:
(list-all-tokens {:query-params {:limit 10}})(list-all-transactions {:keys [query-params]})List all transactions
HTTP Method: GET Endpoint: /v1/issuing/transactions
Query Parameters:
ending_before is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, starting with obj_bar, your subsequent call can include ending_before=obj_bar in order to fetch the previous page of the list.starting_after is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, ending with obj_foo, your subsequent call can include starting_after=obj_foo in order to fetch the next page of the list.capture or refund.Example Usage: (list-all-transactions {:query-params {:limit 10}})
List all transactions
HTTP Method: GET
Endpoint: /v1/issuing/transactions
Query Parameters:
- card (String): Only return transactions that belong to the given card.
- cardholder (String): Only return transactions that belong to the given cardholder.
- created (Unknown): Only return transactions that were created during the given date interval.
- ending-before (String): A cursor for use in pagination. `ending_before` is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, starting with `obj_bar`, your subsequent call can include `ending_before=obj_bar` in order to fetch the previous page of the list.
- expand (Array): Specifies which fields in the response should be expanded.
- limit (Integer): A limit on the number of objects to be returned. Limit can range between 1 and 100, and the default is 10.
- starting-after (String): A cursor for use in pagination. `starting_after` is an object ID that defines your place in the list. For instance, if you make a list request and receive 100 objects, ending with `obj_foo`, your subsequent call can include `starting_after=obj_foo` in order to fetch the next page of the list.
- type (String): Only return transactions that have the given type. One of `capture` or `refund`.
Example Usage:
(list-all-transactions {:query-params {:limit 10}})(post-authorizations-authorization-approve {:keys [authorization-id body]})Approve an authorization
HTTP Method: POST Endpoint: /v1/issuing/authorizations/{authorization-id}/approve
Path Parameters:
Example Usage: (post-authorizations-authorization-approve {:authorization-id example-authorization-id})
Approve an authorization
HTTP Method: POST
Endpoint: /v1/issuing/authorizations/{authorization-id}/approve
Path Parameters:
- authorization-id (String): The authorization-id parameter. (required)
Example Usage:
(post-authorizations-authorization-approve {:authorization-id example-authorization-id})(post-authorizations-authorization-decline {:keys [authorization-id body]})Decline an authorization
HTTP Method: POST Endpoint: /v1/issuing/authorizations/{authorization-id}/decline
Path Parameters:
Example Usage: (post-authorizations-authorization-decline {:authorization-id example-authorization-id})
Decline an authorization
HTTP Method: POST
Endpoint: /v1/issuing/authorizations/{authorization-id}/decline
Path Parameters:
- authorization-id (String): The authorization-id parameter. (required)
Example Usage:
(post-authorizations-authorization-decline {:authorization-id example-authorization-id})(post-disputes-dispute-submit {:keys [dispute-id body]})Submit a dispute
HTTP Method: POST Endpoint: /v1/issuing/disputes/{dispute-id}/submit
Path Parameters:
Example Usage: (post-disputes-dispute-submit {:dispute-id example-dispute-id})
Submit a dispute
HTTP Method: POST
Endpoint: /v1/issuing/disputes/{dispute-id}/submit
Path Parameters:
- dispute-id (String): The dispute-id parameter. (required)
Example Usage:
(post-disputes-dispute-submit {:dispute-id example-dispute-id})(retrieve-authorizations-authorization {:keys [authorization-id query-params]})Retrieve an authorization
HTTP Method: GET Endpoint: /v1/issuing/authorizations/{authorization-id}
Path Parameters:
Query Parameters:
Example Usage: (retrieve-authorizations-authorization {:authorization-id example-authorization-id :query-params {:limit 10}})
Retrieve an authorization
HTTP Method: GET
Endpoint: /v1/issuing/authorizations/{authorization-id}
Path Parameters:
- authorization-id (String): The authorization-id parameter. (required)
Query Parameters:
- expand (Array): Specifies which fields in the response should be expanded.
Example Usage:
(retrieve-authorizations-authorization {:authorization-id example-authorization-id :query-params {:limit 10}})(retrieve-cardholders-cardholder {:keys [cardholder-id query-params]})Retrieve a cardholder
HTTP Method: GET Endpoint: /v1/issuing/cardholders/{cardholder-id}
Path Parameters:
Query Parameters:
Example Usage: (retrieve-cardholders-cardholder {:cardholder-id example-cardholder-id :query-params {:limit 10}})
Retrieve a cardholder
HTTP Method: GET
Endpoint: /v1/issuing/cardholders/{cardholder-id}
Path Parameters:
- cardholder-id (String): The cardholder-id parameter. (required)
Query Parameters:
- expand (Array): Specifies which fields in the response should be expanded.
Example Usage:
(retrieve-cardholders-cardholder {:cardholder-id example-cardholder-id :query-params {:limit 10}})(retrieve-cards-card {:keys [card-id query-params]})Retrieve a card
HTTP Method: GET Endpoint: /v1/issuing/cards/{card-id}
Path Parameters:
Query Parameters:
Example Usage: (retrieve-cards-card {:card-id example-card-id :query-params {:limit 10}})
Retrieve a card
HTTP Method: GET
Endpoint: /v1/issuing/cards/{card-id}
Path Parameters:
- card-id (String): The card-id parameter. (required)
Query Parameters:
- expand (Array): Specifies which fields in the response should be expanded.
Example Usage:
(retrieve-cards-card {:card-id example-card-id :query-params {:limit 10}})(retrieve-disputes-dispute {:keys [dispute-id query-params]})Retrieve a dispute
HTTP Method: GET Endpoint: /v1/issuing/disputes/{dispute-id}
Path Parameters:
Query Parameters:
Example Usage: (retrieve-disputes-dispute {:dispute-id example-dispute-id :query-params {:limit 10}})
Retrieve a dispute
HTTP Method: GET
Endpoint: /v1/issuing/disputes/{dispute-id}
Path Parameters:
- dispute-id (String): The dispute-id parameter. (required)
Query Parameters:
- expand (Array): Specifies which fields in the response should be expanded.
Example Usage:
(retrieve-disputes-dispute {:dispute-id example-dispute-id :query-params {:limit 10}})(retrieve-personalization-designs-personalization-design
{:keys [personalization-design-id query-params]})Retrieve a personalization design
HTTP Method: GET Endpoint: /v1/issuing/personalization_designs/{personalization-design-id}
Path Parameters:
Query Parameters:
Example Usage: (retrieve-personalization-designs-personalization-design {:personalization-design-id example-personalization-design-id :query-params {:limit 10}})
Retrieve a personalization design
HTTP Method: GET
Endpoint: /v1/issuing/personalization_designs/{personalization-design-id}
Path Parameters:
- personalization-design-id (String): The personalization-design-id parameter. (required)
Query Parameters:
- expand (Array): Specifies which fields in the response should be expanded.
Example Usage:
(retrieve-personalization-designs-personalization-design {:personalization-design-id example-personalization-design-id :query-params {:limit 10}})(retrieve-physical-bundles-physical-bundle {:keys [physical-bundle-id
query-params]})Retrieve a physical bundle
HTTP Method: GET Endpoint: /v1/issuing/physical_bundles/{physical-bundle-id}
Path Parameters:
Query Parameters:
Example Usage: (retrieve-physical-bundles-physical-bundle {:physical-bundle-id example-physical-bundle-id :query-params {:limit 10}})
Retrieve a physical bundle
HTTP Method: GET
Endpoint: /v1/issuing/physical_bundles/{physical-bundle-id}
Path Parameters:
- physical-bundle-id (String): The physical-bundle-id parameter. (required)
Query Parameters:
- expand (Array): Specifies which fields in the response should be expanded.
Example Usage:
(retrieve-physical-bundles-physical-bundle {:physical-bundle-id example-physical-bundle-id :query-params {:limit 10}})(retrieve-settlements-settlement {:keys [settlement-id query-params]})Retrieve a settlement
HTTP Method: GET Endpoint: /v1/issuing/settlements/{settlement-id}
Path Parameters:
Query Parameters:
Example Usage: (retrieve-settlements-settlement {:settlement-id example-settlement-id :query-params {:limit 10}})
Retrieve a settlement
HTTP Method: GET
Endpoint: /v1/issuing/settlements/{settlement-id}
Path Parameters:
- settlement-id (String): The settlement-id parameter. (required)
Query Parameters:
- expand (Array): Specifies which fields in the response should be expanded.
Example Usage:
(retrieve-settlements-settlement {:settlement-id example-settlement-id :query-params {:limit 10}})(retrieve-tokens-token {:keys [token-id query-params]})Retrieve an issuing token
HTTP Method: GET Endpoint: /v1/issuing/tokens/{token-id}
Path Parameters:
Query Parameters:
Example Usage: (retrieve-tokens-token {:token-id example-token-id :query-params {:limit 10}})
Retrieve an issuing token
HTTP Method: GET
Endpoint: /v1/issuing/tokens/{token-id}
Path Parameters:
- token-id (String): The token-id parameter. (required)
Query Parameters:
- expand (Array): Specifies which fields in the response should be expanded.
Example Usage:
(retrieve-tokens-token {:token-id example-token-id :query-params {:limit 10}})(retrieve-transactions-transaction {:keys [transaction-id query-params]})Retrieve a transaction
HTTP Method: GET Endpoint: /v1/issuing/transactions/{transaction-id}
Path Parameters:
Query Parameters:
Example Usage: (retrieve-transactions-transaction {:transaction-id example-transaction-id :query-params {:limit 10}})
Retrieve a transaction
HTTP Method: GET
Endpoint: /v1/issuing/transactions/{transaction-id}
Path Parameters:
- transaction-id (String): The transaction-id parameter. (required)
Query Parameters:
- expand (Array): Specifies which fields in the response should be expanded.
Example Usage:
(retrieve-transactions-transaction {:transaction-id example-transaction-id :query-params {:limit 10}})(update-authorizations-authorization {:keys [authorization-id body]})Update an authorization
HTTP Method: POST Endpoint: /v1/issuing/authorizations/{authorization-id}
Path Parameters:
Example Usage: (update-authorizations-authorization {:authorization-id example-authorization-id})
Update an authorization
HTTP Method: POST
Endpoint: /v1/issuing/authorizations/{authorization-id}
Path Parameters:
- authorization-id (String): The authorization-id parameter. (required)
Example Usage:
(update-authorizations-authorization {:authorization-id example-authorization-id})(update-cardholders-cardholder {:keys [cardholder-id body]})Update a cardholder
HTTP Method: POST Endpoint: /v1/issuing/cardholders/{cardholder-id}
Path Parameters:
Example Usage: (update-cardholders-cardholder {:cardholder-id example-cardholder-id})
Update a cardholder
HTTP Method: POST
Endpoint: /v1/issuing/cardholders/{cardholder-id}
Path Parameters:
- cardholder-id (String): The cardholder-id parameter. (required)
Example Usage:
(update-cardholders-cardholder {:cardholder-id example-cardholder-id})(update-cards-card {:keys [card-id body]})Update a card
HTTP Method: POST Endpoint: /v1/issuing/cards/{card-id}
Path Parameters:
Example Usage: (update-cards-card {:card-id example-card-id})
Update a card
HTTP Method: POST
Endpoint: /v1/issuing/cards/{card-id}
Path Parameters:
- card-id (String): The card-id parameter. (required)
Example Usage:
(update-cards-card {:card-id example-card-id})(update-disputes-dispute {:keys [dispute-id body]})Update a dispute
HTTP Method: POST Endpoint: /v1/issuing/disputes/{dispute-id}
Path Parameters:
Example Usage: (update-disputes-dispute {:dispute-id example-dispute-id})
Update a dispute
HTTP Method: POST
Endpoint: /v1/issuing/disputes/{dispute-id}
Path Parameters:
- dispute-id (String): The dispute-id parameter. (required)
Example Usage:
(update-disputes-dispute {:dispute-id example-dispute-id})(update-personalization-designs-personalization-design
{:keys [personalization-design-id body]})Update a personalization design
HTTP Method: POST Endpoint: /v1/issuing/personalization_designs/{personalization-design-id}
Path Parameters:
Example Usage: (update-personalization-designs-personalization-design {:personalization-design-id example-personalization-design-id})
Update a personalization design
HTTP Method: POST
Endpoint: /v1/issuing/personalization_designs/{personalization-design-id}
Path Parameters:
- personalization-design-id (String): The personalization-design-id parameter. (required)
Example Usage:
(update-personalization-designs-personalization-design {:personalization-design-id example-personalization-design-id})(update-settlements-settlement {:keys [settlement-id body]})Update a settlement
HTTP Method: POST Endpoint: /v1/issuing/settlements/{settlement-id}
Path Parameters:
Example Usage: (update-settlements-settlement {:settlement-id example-settlement-id})
Update a settlement
HTTP Method: POST
Endpoint: /v1/issuing/settlements/{settlement-id}
Path Parameters:
- settlement-id (String): The settlement-id parameter. (required)
Example Usage:
(update-settlements-settlement {:settlement-id example-settlement-id})(update-tokens-token {:keys [token-id body]})Update a token status
HTTP Method: POST Endpoint: /v1/issuing/tokens/{token-id}
Path Parameters:
Example Usage: (update-tokens-token {:token-id example-token-id})
Update a token status
HTTP Method: POST
Endpoint: /v1/issuing/tokens/{token-id}
Path Parameters:
- token-id (String): The token-id parameter. (required)
Example Usage:
(update-tokens-token {:token-id example-token-id})(update-transactions-transaction {:keys [transaction-id body]})Update a transaction
HTTP Method: POST Endpoint: /v1/issuing/transactions/{transaction-id}
Path Parameters:
Example Usage: (update-transactions-transaction {:transaction-id example-transaction-id})
Update a transaction
HTTP Method: POST
Endpoint: /v1/issuing/transactions/{transaction-id}
Path Parameters:
- transaction-id (String): The transaction-id parameter. (required)
Example Usage:
(update-transactions-transaction {:transaction-id example-transaction-id})cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |