refundAuthorization.accepted.event.v1 (v1.5.0)
Exchange: payment
refundId string <guid>
requiredMatch pattern:
^[a-fA-F0-9]{32}$Min length:
1merchantId string <guid>
requiredMatch pattern:
^[a-fA-F0-9]{32}$Min length:
1merchantAccountId nullstring <guid>
Match pattern:
^[a-fA-F0-9]{32}$partnerId nullstring <guid>
Match pattern:
^[a-fA-F0-9]{32}$paymentId string <guid>
requiredMatch pattern:
^[a-fA-F0-9]{32}$Min length:
1header object → EventHeader
auditLog object → AuditLog
userId string
requiredMin length:
1Max length:
128userRoles array [string]
created string <date-time>
requiredMin length:
1messageId string <guid>
requiredMatch pattern:
^[a-fA-F0-9]{32}$Min length:
1correlationId nullstring <guid>
Match pattern:
^[a-fA-F0-9]{32}$messageVersion string
requiredMajor.minor --> 1.12 Each change on the message will increase the minor version
Min length:
1Max length:
128publisherId string
requiredMin length:
1Max length:
128messageName string
aggregateId string <guid>
requiredeg. PaymentId
Match pattern:
^[a-fA-F0-9]{32}$Min length:
1aggregateType string
requiredAggregate root, eg. \"payment\", \"merchant\"
Min length:
1aggregateSequenceNumber integer <int32>
requiredStarting at 1.
amount object → Amount_
requiredamount integer <int64>
requiredcurrency string
requiredISO-4217 Code (3 char codes, e.g. SEK,NOK,EUR,DKK)
Match pattern:
^[A-Z]{3}$Min length:
1forceRetryOfExternalRefund booleannull
This is not a part of the public message schema. We need this property so that we can manipulate the refund auth accepted before putting it back on queue. We have a blind-spot in our Swish refund flow if we have a network error when calling Swish. If we call Swish and they say that they have not registered the refund in such a case. Set this to true and move it back to queue so that we can retry the refund against Swish.
No properties match your search
Try a different search term or clear the search to see all properties