POST /issue
Issues a new card of the given payment method.
Servers
- https://pal-test.adyen.com/pal/servlet/StoredValue/v46
Request headers
Name | Type | Required | Description |
---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
Name | Type | Required | Description |
---|---|---|---|
paymentMethod |
Object | Yes |
The collection that contains the type of the payment method and its specific information if available |
shopperInteraction |
String | No |
Specifies the sales channel, through which the shopper gives their card details, and whether the shopper is a returning customer. For the web service API, Adyen assumes Ecommerce shopper interaction by default. This field has the following possible values:
Possible values:
|
shopperReference |
String | No | |
recurringDetailReference |
String | No | |
amount |
Object | No |
The amount information for the transaction. |
amount.value |
Integer | Yes |
The amount of the transaction, in minor units. |
amount.currency |
String | Yes |
The three-character ISO currency code. |
merchantAccount |
String | Yes |
The merchant account identifier, with which you want to process the transaction. |
reference |
String | Yes |
The reference to uniquely identify a payment. This reference is used in all communication with you about the payment status. We recommend using a unique value per payment; however, it is not a requirement. If you need to provide multiple references for a transaction, separate them with hyphens ("-"). Maximum length: 80 characters. |
store |
String | No |
The physical store, for which this payment is processed. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.