Operations
activate
Request a gift card activation.
POST /activations/{activationId}
The Activations endpoint allows a gift card to be activated. Optionally, an amount can be included to indicate initial funds which should be credited to the card. An activation is not considered complete until an activation confirmation or activation reversal has been sent and acknowledged. An activation request should only be sent once.
Security
- httpBasic
Request
Content-Type: application/json
Parameters
| Name | Located in | Required | Description | Default | Schema |
|---|---|---|---|---|---|
| activationId | path | yes | The randomly generated UUID identifying this activation, as defined for a variant 4 UUID in RFC 4122. | string | |
| body | body | yes | The activation information. | ActivationRequest |
Response
Content-Type: application/json
| Status Code | Reason | Response Model |
|---|---|---|
| 201 | Created | ActivationResponse |
| 400 | Bad Request | ErrorDetail |
| 500 | Internal Server Error | ErrorDetail |
| 503 | Service Unavailable | ErrorDetail |
| 504 | Gateway Timeout | ErrorDetail |
confirmActivation
Confirm a gift card activation.
POST /activations/{activationId}/confirmations/{confirmationId}
The Activation Confirmations endpoint registers the confirmation of a prior activation of a giftcard. Activation confirmations are advice type messages and should continue to be sent at suitable intervals until a response has been received. Multiple confirmation advices may be sent which refer to the same activation. The net result is that the activation is confirmed once.
Security
- httpBasic
Request
Content-Type: application/json
Parameters
| Name | Located in | Required | Description | Default | Schema |
|---|---|---|---|---|---|
| activationId | path | yes | The randomly generated activationId UUID as sent in the original activation. | string | |
| confirmationId | path | yes | The randomly generated UUID identifying this confirmation, as defined for a variant 4 UUID in RFC 4122. | string | |
| body | body | yes | The activation confirmation information. | ActivationConfirmation |
Response
Content-Type: application/json
| Status Code | Reason | Response Model |
|---|---|---|
| 202 | Accepted | BasicAdvice |
| 400 | Bad Request | ErrorDetail |
| 404 | Not Found | ErrorDetail |
| 500 | Internal Server Error | ErrorDetail |
| 503 | Service Unavailable | ErrorDetail |
| 504 | Gateway Timeout | ErrorDetail |
reverseActivation
Simplistically, an activation reversal undoes an activation if the activation was successfully processed.
POST /activations/{activationId}/reversals/{reversalId}
The Activation Reversals endpoint allows an activation of a giftcard to be reversed. If the sender of an activation request is uncertain of the state of an activation request then the sender must send an activation reversal. Activation reversals are advice type messages and should continue to be sent at suitable intervals until a response has been received. Multiple reversals advices may be sent which refer to the same activation. The net result is that the activation is reversed once.
Security
- httpBasic
Request
Content-Type: application/json
Parameters
| Name | Located in | Required | Description | Default | Schema |
|---|---|---|---|---|---|
| activationId | path | yes | The randomly generated activationId UUID as sent in the original activation. | string | |
| reversalId | path | yes | The randomly generated UUID identifying this reversal, as defined for a variant 4 UUID in RFC 4122. | string | |
| body | body | yes | The activation reversal information. | ActivationReversal |
Response
Content-Type: application/json
| Status Code | Reason | Response Model |
|---|---|---|
| 202 | Accepted | BasicAdvice |
| 400 | Bad Request | ErrorDetail |
| 404 | Not Found | ErrorDetail |
| 500 | Internal Server Error | ErrorDetail |
| 503 | Service Unavailable | ErrorDetail |
| 504 | Gateway Timeout | ErrorDetail |
load
Request funds to be loaded on a gift card.
POST /loads/{loadId}
The Loads endpoint allows loading of funds on a gift card to be authorized. A load is not considered complete until a load confirmation or load reversal has been sent and acknowledged. A load request should only be sent once otherwise multiple loads may occur erroneously.
Security
- httpBasic
Request
Content-Type: application/json
Parameters
| Name | Located in | Required | Description | Default | Schema |
|---|---|---|---|---|---|
| loadId | path | yes | The randomly generated UUID identifying this load, as defined for a variant 4 UUID in RFC 4122. | string | |
| body | body | yes | The load information. | LoadRequest |
Response
Content-Type: application/json
| Status Code | Reason | Response Model |
|---|---|---|
| 201 | Created | LoadResponse |
| 400 | Bad Request | ErrorDetail |
| 500 | Internal Server Error | ErrorDetail |
| 503 | Service Unavailable | ErrorDetail |
| 504 | Gateway Timeout | ErrorDetail |
confirmLoad
Confirm a load of funds on a gift card.
POST /loads/{loadId}/confirmations/{confirmationId}
The Load Confirmations endpoint registers the confirmation of a prior load on a gift card. Load confirmations are advice type messages and should continue to be sent at suitable intervals until a response has been received. Multiple confirmation advices may be sent which refer to the same load. The net result is that the load is confirmed once.
Security
- httpBasic
Request
Content-Type: application/json
Parameters
| Name | Located in | Required | Description | Default | Schema |
|---|---|---|---|---|---|
| loadId | path | yes | The randomly generated loadId UUID as sent in the original load. | string | |
| confirmationId | path | yes | The randomly generated UUID identifying this confirmation, as defined for a variant 4 UUID in RFC 4122. | string | |
| body | body | yes | The load confirmation information. | LoadConfirmation |
Response
Content-Type: application/json
| Status Code | Reason | Response Model |
|---|---|---|
| 202 | Accepted | BasicAdvice |
| 400 | Bad Request | ErrorDetail |
| 404 | Not Found | ErrorDetail |
| 500 | Internal Server Error | ErrorDetail |
| 503 | Service Unavailable | ErrorDetail |
| 504 | Gateway Timeout | ErrorDetail |
reverseLoad
Simplistically, a load reversal undoes a load if the load was successfully processed.
POST /loads/{loadId}/reversals/{reversalId}
The Load Reversals endpoint allows loads on a gift card to be reversed. If the sender of a load request is uncertain of the state of a load request then the sender must send a load reversal. Reversals should continue to be sent at suitable intervals until a response has been received. Multiple reversals may be sent which refer to the same load. The net result is that the load is reversed once. Note that a load reversal does not equate to a redemption.
Security
- httpBasic
Request
Content-Type: application/json
Parameters
| Name | Located in | Required | Description | Default | Schema |
|---|---|---|---|---|---|
| loadId | path | yes | The randomly generated loadId UUID as sent in the original load. | string | |
| reversalId | path | yes | The randomly generated UUID identifying this reversal, as defined for a variant 4 UUID in RFC 4122. | string | |
| body | body | yes | The redemption reversal information. | LoadReversal |
Response
Content-Type: application/json
| Status Code | Reason | Response Model |
|---|---|---|
| 202 | Accepted | BasicAdvice |
| 400 | Bad Request | ErrorDetail |
| 404 | Not Found | ErrorDetail |
| 500 | Internal Server Error | ErrorDetail |
| 503 | Service Unavailable | ErrorDetail |
| 504 | Gateway Timeout | ErrorDetail |
lookupGiftcard
Request gift card information.
POST /lookupGiftcard/{lookupId}
The Lookup Gift Cards endpoint allows information about a gift card to be retrieved. This operation has no financial impact and may be submitted repeatedly without financial consequece. Thus there is no confirmation or reversal process for gift card lookup requests.
Security
- httpBasic
Request
Content-Type: application/json
Parameters
| Name | Located in | Required | Description | Default | Schema |
|---|---|---|---|---|---|
| lookupId | path | yes | The randomly generated UUID identifying this lookup request, as defined for a variant 4 UUID in RFC 4122. | string | |
| body | body | yes | Information describing the gift card lookup to be performed. | LookupRequest |
Response
Content-Type: application/json
| Status Code | Reason | Response Model |
|---|---|---|
| 201 | Created | LookupResponse |
| 400 | Bad Request | ErrorDetail |
| 404 | Not Found | ErrorDetail |
| 500 | Internal Server Error | ErrorDetail |
| 503 | Service Unavailable | ErrorDetail |
| 504 | Gateway Timeout | ErrorDetail |
redemption
Request a redemption of a gift card.
POST /redemptions/{redemptionId}
The Redemptions endpoint allows gift cards to be redeemed as a form of tender. A redemption is not considered complete until a redemption confirmation or redemption reversal has been sent and acknowledged. A redemption request should only be sent once otherwise multiple redemptions may occur erroneously.
Security
- httpBasic
Request
Content-Type: application/json
Parameters
| Name | Located in | Required | Description | Default | Schema |
|---|---|---|---|---|---|
| redemptionId | path | yes | The randomly generated UUID identifying this redemption, as defined for a variant 4 UUID in RFC 4122. | string | |
| body | body | yes | The redemption information. | RedemptionRequest |
Response
Content-Type: application/json
| Status Code | Reason | Response Model |
|---|---|---|
| 201 | Created | RedemptionResponse |
| 400 | Bad Request | ErrorDetail |
| 500 | Internal Server Error | ErrorDetail |
| 503 | Service Unavailable | ErrorDetail |
| 504 | Gateway Timeout | ErrorDetail |
confirmRedemption
Confirm a redemption against a gift card.
POST /redemptions/{redemptionId}/confirmations/{confirmationId}
The Redemption Confirmations endpoint registers the confirmation of a prior redemption of a gift card. Redemption confirmations are advice type messages and should continue to be sent at suitable intervals until a response has been received. Multiple confirmation advices may be sent which refer to the same redemption. The net result is that the redemption is confirmed once.
Security
- httpBasic
Request
Content-Type: application/json
Parameters
| Name | Located in | Required | Description | Default | Schema |
|---|---|---|---|---|---|
| redemptionId | path | yes | The randomly generated redemptionId UUID as sent in the original redemption. | string | |
| confirmationId | path | yes | The randomly generated UUID identifying this confirmation, as defined for a variant 4 UUID in RFC 4122. | string | |
| body | body | yes | The redemption confirmation information. | RedemptionConfirmation |
Response
Content-Type: application/json
| Status Code | Reason | Response Model |
|---|---|---|
| 202 | Accepted | BasicAdvice |
| 400 | Bad Request | ErrorDetail |
| 404 | Not Found | ErrorDetail |
| 500 | Internal Server Error | ErrorDetail |
| 503 | Service Unavailable | ErrorDetail |
| 504 | Gateway Timeout | ErrorDetail |
reverseRedemption
Simplistically, a redemption reversal undoes a redemption if the redemption was successfully processed.
POST /redemptions/{redemptionId}/reversals/{reversalId}
The Redemption Reversals endpoint allows redemptions on a gift card to be reversed. If the sender of a redemption request is uncertain of the state of a redemption request then the sender must send a redemption reversal. Reversals should continue to be sent at suitable intervals until a response has been received. Multiple reversals may be sent which refer to the same redemption. The net result is that the redemption is reversed once. Note that a reversal does not equate to a load.
Security
- httpBasic
Request
Content-Type: application/json
Parameters
| Name | Located in | Required | Description | Default | Schema |
|---|---|---|---|---|---|
| redemptionId | path | yes | The randomly generated redemptionId UUID as sent in the original redemption. | string | |
| reversalId | path | yes | The randomly generated UUID identifying this reversal, as defined for a variant 4 UUID in RFC 4122. | string | |
| body | body | yes | The redemption reversal information. | RedemptionReversal |
Response
Content-Type: application/json
| Status Code | Reason | Response Model |
|---|---|---|
| 202 | Accepted | BasicAdvice |
| 400 | Bad Request | ErrorDetail |
| 404 | Not Found | ErrorDetail |
| 500 | Internal Server Error | ErrorDetail |
| 503 | Service Unavailable | ErrorDetail |
| 504 | Gateway Timeout | ErrorDetail |
replace
Request a replace of an old gift card with a new gift card.
POST /replaces/{replaceId}
The Replace endpoint allows old gift cards to be replaced with new gift cards (transfers all funds and voids old card). A replace is not considered complete until a replace confirmation or replace reversal has been sent and acknowledged. A replace request should only be sent once otherwise multiple replace requests may occur erroneously.
Security
- httpBasic
Request
Content-Type: application/json
Parameters
| Name | Located in | Required | Description | Default | Schema |
|---|---|---|---|---|---|
| replaceId | path | yes | The randomly generated UUID identifying this replace, as defined for a variant 4 UUID in RFC 4122. | string | |
| body | body | yes | The replace information. | ReplaceRequest |
Response
Content-Type: application/json
| Status Code | Reason | Response Model |
|---|---|---|
| 201 | Created | ReplaceResponse |
| 400 | Bad Request | ErrorDetail |
| 500 | Internal Server Error | ErrorDetail |
| 503 | Service Unavailable | ErrorDetail |
| 504 | Gateway Timeout | ErrorDetail |
confirmReplace
Confirm a replace request of an old card with a new card.
POST /replaces/{replaceId}/confirmations/{confirmationId}
The Replace Confirmations endpoint registers the confirmation of a prior replace request for an old gift card to be replaced by a new gift card. Replace confirmations are advice type messages and should continue to be sent at suitable intervals until a response has been received. Multiple confirmation advices may be sent which refer to the same replace request. The net result is that the replace request is confirmed once.
Security
- httpBasic
Request
Content-Type: application/json
Parameters
| Name | Located in | Required | Description | Default | Schema |
|---|---|---|---|---|---|
| replaceId | path | yes | The randomly generated replaceId UUID as sent in the original replace request. | string | |
| confirmationId | path | yes | The randomly generated UUID identifying this confirmation, as defined for a variant 4 UUID in RFC 4122. | string | |
| body | body | yes | The replace confirmation information. | ReplaceConfirmation |
Response
Content-Type: application/json
| Status Code | Reason | Response Model |
|---|---|---|
| 202 | Accepted | BasicAdvice |
| 400 | Bad Request | ErrorDetail |
| 404 | Not Found | ErrorDetail |
| 500 | Internal Server Error | ErrorDetail |
| 503 | Service Unavailable | ErrorDetail |
| 504 | Gateway Timeout | ErrorDetail |
reverseReplace
Simplistically, a replace reversal undoes a replace request if the replace was successfully processed.
POST /replaces/{replaceId}/reversals/{reversalId}
The Replace Reversals endpoint allows replace requests of old gift cards with a new gift cards to be reversed. If the sender of a replace request is uncertain of the state of a replace request then the sender must send a replace reversal. Reversals should continue to be sent at suitable intervals until a response has been received. Multiple reversals may be sent which refer to the same replace request. The net result is that the replace request is reversed once.
Security
- httpBasic
Request
Content-Type: application/json
Parameters
| Name | Located in | Required | Description | Default | Schema |
|---|---|---|---|---|---|
| replaceId | path | yes | The randomly generated replaceId UUID as sent in the original replace. | string | |
| reversalId | path | yes | The randomly generated UUID identifying this reversal, as defined for a variant 4 UUID in RFC 4122. | string | |
| body | body | yes | The replace reversal information. | ReplaceReversal |
Response
Content-Type: application/json
| Status Code | Reason | Response Model |
|---|---|---|
| 202 | Accepted | BasicAdvice |
| 400 | Bad Request | ErrorDetail |
| 404 | Not Found | ErrorDetail |
| 500 | Internal Server Error | ErrorDetail |
| 503 | Service Unavailable | ErrorDetail |
| 504 | Gateway Timeout | ErrorDetail |
transfer
Request a transfer from a source gift card to a target gift card.
POST /transfers/{transferId}
The Transfers endpoint allows funds to be transferred from one gift card to another. A transfer is not considered complete until a transfer confirmation or transfer reversal has been sent and acknowledged. A transfer request should only be sent once otherwise multiple transfers may occur erroneously.
Security
- httpBasic
Request
Content-Type: application/json
Parameters
| Name | Located in | Required | Description | Default | Schema |
|---|---|---|---|---|---|
| transferId | path | yes | The randomly generated UUID identifying this transfer, as defined for a variant 4 UUID in RFC 4122. | string | |
| body | body | yes | The transfer information. | TransferRequest |
Response
Content-Type: application/json
| Status Code | Reason | Response Model |
|---|---|---|
| 201 | Created | TransferResponse |
| 400 | Bad Request | ErrorDetail |
| 500 | Internal Server Error | ErrorDetail |
| 503 | Service Unavailable | ErrorDetail |
| 504 | Gateway Timeout | ErrorDetail |
confirmTransfer
Confirm a transfer from a source gift card to a target gift card.
POST /transfers/{transferId}/confirmations/{confirmationId}
The Transfer Confirmations endpoint registers the confirmation of a prior transfer of a source gift card to a target gift card. Transfer confirmations are advice type messages and should continue to be sent at suitable intervals until a response has been received. Multiple confirmation advices may be sent which refer to the same transfer. The net result is that the transfer is confirmed once.
Security
- httpBasic
Request
Content-Type: application/json
Parameters
| Name | Located in | Required | Description | Default | Schema |
|---|---|---|---|---|---|
| transferId | path | yes | The randomly generated transferId UUID as sent in the original transfer request. | string | |
| confirmationId | path | yes | The randomly generated UUID identifying this confirmation, as defined for a variant 4 UUID in RFC 4122. | string | |
| body | body | yes | The transfer confirmation information. | TransferConfirmation |
Response
Content-Type: application/json
| Status Code | Reason | Response Model |
|---|---|---|
| 202 | Accepted | BasicAdvice |
| 400 | Bad Request | ErrorDetail |
| 404 | Not Found | ErrorDetail |
| 500 | Internal Server Error | ErrorDetail |
| 503 | Service Unavailable | ErrorDetail |
| 504 | Gateway Timeout | ErrorDetail |
reverseTransfer
Simplistically, a transfer reversal undoes a transfer if the transfer was successfully processed.
POST /transfers/{transferId}/reversals/{reversalId}
The Transfer Reversals endpoint allows a transfer between gift cards to be reversed. If the sender of a transfer request is uncertain of the state of a transfer request then the sender must send a transfer reversal. Reversals should continue to be sent at suitable intervals until a response has been received. Multiple reversals may be sent which refer to the same transfer. The net result is that the transfer is reversed once.
Security
- httpBasic
Request
Content-Type: application/json
Parameters
| Name | Located in | Required | Description | Default | Schema |
|---|---|---|---|---|---|
| transferId | path | yes | The randomly generated transferId UUID as sent in the original transfer. | string | |
| reversalId | path | yes | The randomly generated UUID identifying this reversal, as defined for a variant 4 UUID in RFC 4122. | string | |
| body | body | yes | The transfer reversal information. | TransferReversal |
Response
Content-Type: application/json
| Status Code | Reason | Response Model |
|---|---|---|
| 202 | Accepted | BasicAdvice |
| 400 | Bad Request | ErrorDetail |
| 404 | Not Found | ErrorDetail |
| 500 | Not Found | ErrorDetail |
| 503 | Service Unavailable | ErrorDetail |
| 504 | Gateway Timeout | ErrorDetail |
void
Request a gift card be voided.
POST /voids/{voidId}
The Voids endpoint allows an activated giftcard to be voided. A void is not considered complete until a void confirmation or void reversal has been sent and acknowledged. While a gift card can only be voided once, a void request should only be sent once and then either confirmed or reversed.
Security
- httpBasic
Request
Content-Type: application/json
Parameters
| Name | Located in | Required | Description | Default | Schema |
|---|---|---|---|---|---|
| voidId | path | yes | The randomly generated UUID identifying this void, as defined for a variant 4 UUID in RFC 4122. | string | |
| body | body | yes | The void information. | VoidRequest |
Response
Content-Type: application/json
| Status Code | Reason | Response Model |
|---|---|---|
| 200 | successful operation | VoidResponse |
| 201 | Created | VoidResponse |
| 400 | Bad Request | ErrorDetail |
| 500 | Internal Server Error | ErrorDetail |
| 503 | Service Unavailable | ErrorDetail |
| 504 | Gateway Timeout | ErrorDetail |
confirmVoid
Confirm a void of a gift card.
POST /voids/{voidId}/confirmations/{confirmationId}
The Void Confirmations endpoint registers the confirmation of a prior void on a gift card. Void confirmations are advice type messages and should continue to be sent at suitable intervals until a response has been received. Multiple confirmation advices may be sent which refer to the same void. The net result is that the void is confirmed once.
Security
- httpBasic
Request
Content-Type: application/json
Parameters
| Name | Located in | Required | Description | Default | Schema |
|---|---|---|---|---|---|
| voidId | path | yes | The randomly generated voidId UUID as sent in the original void. | string | |
| confirmationId | path | yes | The randomly generated UUID identifying this confirmation, as defined for a variant 4 UUID in RFC 4122. | string | |
| body | body | yes | The void confirmation information. | VoidConfirmation |
Response
Content-Type: application/json
| Status Code | Reason | Response Model |
|---|---|---|
| 202 | Accepted | BasicAdvice |
| 400 | Bad Request | ErrorDetail |
| 404 | Not Found | ErrorDetail |
| 500 | Internal Server Error | ErrorDetail |
| 503 | Service Unavailable | ErrorDetail |
| 504 | Gateway Timeout | ErrorDetail |
reverseVoid
Simplistically, a void reversal undoes a void if the void was successfully processed.
POST /voids/{voidId}/reversals/{reversalId}
The Void Reversals endpoint allows voids of a gift card to be reversed. If the sender of a void request is uncertain of the state of a void request then the sender must send a void reversal. Reversals should continue to be sent at suitable intervals until a response has been received. Multiple reversals may be sent which refer to the same void. The net result is that the void is reversed once.
Security
- httpBasic
Request
Content-Type: application/json
Parameters
| Name | Located in | Required | Description | Default | Schema |
|---|---|---|---|---|---|
| voidId | path | yes | The randomly generated voidId UUID as sent in the original void. | string | |
| reversalId | path | yes | The randomly generated UUID identifying this reversal, as defined for a variant 4 UUID in RFC 4122. | string | |
| body | body | yes | The void reversal information. | VoidReversal |
Response
Content-Type: application/json
| Status Code | Reason | Response Model |
|---|---|---|
| 202 | Accepted | BasicAdvice |
| 400 | Bad Request | ErrorDetail |
| 404 | Not Found | ErrorDetail |
| 500 | Internal Server Error | ErrorDetail |
| 503 | Service Unavailable | ErrorDetail |
| 504 | Gateway Timeout | ErrorDetail |