Read a Smart Transaction

To check the status you need to read the Smart Transaction:

Request

GET /api/v2/Smart/Transactions/STX_33PXAW2YN2NJTPM5KPGMK7QF5PBVA2 HTTP/1.1
Host: connect-testing.secupay-ag.de
Authorization: Bearer qb56tjj1bcvo9n2nj4u38k84lo
Accept: application/json

If everything is fine, the API responds with 200 OK: and the object representation:

Response

HTTP/1.1 200 OK
Content-Type: application/json
...
  
{
    "object": "smart.transactions",
    "id": "STX_33PXAW2YN2NJTPM5KPGMK7QF5PBVA2",
    // ...
    "transactions": [
        {
            "object": "payment.transactions",
            "id": "PCI_FDBREW9ZS7P6FTN4ZY2ATC6NK0QWO7"
        }
    ],
    "created": "2020-03-27T10:55:23+01:00",
    "updated": "2020-03-27T10:56:41+01:00",
    "status": "ok",
    // ...
}

The status of the Smart Transaction will be ok (intent sale), received (intent order and shipping), or collection (intent order and collection). If you have to wait for the payment before you deliver, the status is pending. This can happen with advance payment (prepaid) and occassionally with SEPA direct debit.

This is the status flow of a Smart Transaction for e-commerce including loyalty:

images/inline/e96d988574213906da42d8ada425bb34c453c8a7.png

Some of the statuses will be skipped if they are not needed.

Though loyalty functions are subject to another guide, the additional status processing is contained here for completeness.

Detailed explanation:

Status	Description
`created`	Newly created Smart Transaction, modified before the payment was actually captured.
`processing`	The secucard in the `idents` array is applied for partial payment. The amount of `missing_sum` needs to be paid with another means of payment. Only used if `/preTransaction` is called.
`approved`	The payment is pre-authorised. It should be possible to capture the payment. Skipped if `auto_capture` is `true`.
`pending`	The payment capture has been requested, but is not acknowledged so far. You need to wait for status `ok`, `received` or `collection`. Always used with advance payment (`prepaid`). Can also occur with direct debiting (`debit`).
`ok`	The payment capture was approved and you can deliver. This is used in conjunction with plain payments (intent `sale`). Note: Please don't forget to mark delivery in conjuction with invoice payment (`invoice`). Otherwise we cannot be aware of the due date.
`received`	The payment capture was approved and you can ship the goods. This is used in conjunction with orders for shipping (intent `order`, delivery type `shipping`). Note: Please don't forget to mark delivery, especially in conjuction with invoice payment (`invoice`).
`shipped`	You have shipped the goods.
`collection`	The payment capture was approved and you can prepare the goods for collection, or alternatively ship them. This is used in conjunction with orders for collection (intent `order`, delivery type `collection`). Note: Please don't forget to mark delivery, especially in conjuction with invoice payment (`invoice`).
`collected`	The goods have been collected by your customer.
`failed`	Failed to authorise or capture the payment.