sequenceIdproperty which can be used to cross reference related transactions. For example, a pending transaction may have already been partially transacted and have related debit transactions (for more information on transaction states, see here).
detailproperty which includes some supplementary information. For more information, see here.
pending, it has entered the first state of authorization and is currently awaiting to be debited, or further action. A transaction that is pending will typically be completely debited, thus deleting the existing pending transaction, and being replaced with a
debittransaction. A transaction can be partially debited however, which means that a new
debittransaction record will be created for each partial debit.
pendingtransaction record will continue to persist until its value has been decreased to 0, either via debits or reversal charges. Reversals will not be recorded via the transaction records, except through the decreasing value of the
pendingtransaction. This is not to be confused with a
refundtransaction, which will generate a new transaction record.
complete, it has entered a state that represents a successful debit. A completed transaction can be associated with a previously pending transaction via the
sequenceIdif the completed transaction was a partial debit.
refund, it means that a previously transacted record (state is
complete) has been refunded. This can be either for a partial amount or the full amount. If a transaction is refunded, it will not remove the
decline, it means that an error has occurred while attempting to process a transaction. For more information on decline reasons, see here.
detailproperty. Pending, complete, and refund transactions will always contain at least 1 detail. The information contained in details is recorded below:
listTransactionsWithFiltercan be used on iOS or the two APIs
listTransactionscan be used on Android.
id, whereas the latter is sued to access a list of transactions. Both of these APIs support the use of data Caching through the use of the
getTransactionWithIdcan be used. If the input
idproperty does not match an existing record, a
nilresponse will be returned.
listTransactionsWithFiltermay be used. If no results matching the input are found, an empty list will be returned.
unsubscribeAllAPIs allow you to start and stop receiving updates.
typefield of the transaction will be
PENDING. Some time later you will receive another update with the