Changes
There are 3 types of changes: transaction, subscriber and charge. All fields are always present and have valid default values.
Transaction
In this context, transactions are regular payment transactions.
| JSON fields | Description |
|---|---|
"type": "transaction"
|
Type denoting that this is a transaction. |
"id": 378
|
The transaction ID. |
"rev": 3
|
A revision number. It starts at 1 and it increments every time the transaction data changes.
|
"locked": "u7812:4"
|
Whether or not this transaction has been made immutable and if so, which API key was responsible. |
|
|
|
A list of services used when authorizing this transaction. In addition to the acquiring agreement in the form seen in the dashboard (eg. "clearhaus-1" or "nets-3") these are the currently supported additional services:
"3dsecurev2",
"applepay",
"mobilepay".
The legacy services "3dsecure" and "dsbn" can appear on older entries, denoting 3-D Secure before version 2 and the first version of Dankort Secured by Nets.
|
|
Information about the use pattern of the payment window by the payer.
|
|
Unix timestamps denoting
|
"orderid": "00029384",
|
The order ID that you assigned to the transaction when creating the payment link. |
|
The shipping and billing addresses that were given when creating the payment link. |
|
The array of items that were given when creating the payment link. Note: the "quantity" field defaults to 1 if none was specified.
|
|
A chronologically ordered array of actions performed on this transaction. There are 3 types of actions:
"history" array contains meta-data about the action which is used in the dashboard to show, for example, which items have been captured. The data is not checked for correctness and may be invalid or missing.
|
|
An associative array of fees you were charged by us for the authorization. There are currently no fees for any authorizations. |
|
The sum totals of all actions performed on this transaction.
|
Charge
Charges are transactions with payment window data missing and some extra information about the subcriber that was charged.
| JSON fields | Description |
|---|---|
"type": "charge"
|
Type denoting that this is a subscriber charge. Note: charges functionally are transactions. The difference in data here is purely cosmetic. |
"info": {}
|
Unlike for regular transactions, this object is not returned. |
|
|
Subscriber
| JSON fields | Description |
|---|---|
"type": "subscriber"
|
Type denoting that this is a subscriber. |
"id": 19
|
The subscriber ID. |
"rev": 2
|
A revision number. It starts at 1 and it increments every time the subcriber data changes.
|
"ref": "user301"
|
The reference ID that you assigned to the subscriber when you created it. |
|
|
|
Unix timestamps denoting
|
|
Information about the payer whose credentials got stored when first creating or last renewing the subscriber.
|
|
The shipping and billing addresses that were supplied when creating or last renewing the subscriber. |
|
A chronologically ordered array of actions performed on this subscriber. There is currently only 1 type of action:
"nets-2" or "clearhaus-1") there is currently only 1 supported service: "3dsecurev2".
The legacy services "3dsecure" and "dsbn" can appear on older entries, denoting 3-D Secure before version 2 and the first version of Dankort Secured by Nets.
|