
Receipts (SendResponse)
Receipts, such as Positive (ACK) and Negative acknowledgments (NACK) will be sent to you as a Send Response. The SendResponse will be available in the from-peppol folder for each file sent to Peppol. A successful send from your AP to the receiver’s Peppol Access Point you will get an ACK with statuscode ‘200’.
If an error occurred you will receive a NACK with status code ‘500’ with one or more error codes along with descriptions. Check here to see all error codes
Filename pattern conventions
ACK/NACKs are named RCPT{RelayOperatorId}-{EpochTimestamp}.xml, such as RCPT1948-1430650437914.xml.
Late 2019 we are launching Galaxy Gateway 2.0 and the filename pattern will then change to {RCPT|DLVY}-{RelayOperatorId}-{UUID}.xml. Please make sure that you can handle both patterns when fetching files from the SFTP server.
Files from Peppol to you are named DLVY{RelayOperatorId}-{EpochTimestamp}.xml, such as DLVY1948-1430476414164.xml.
Learn more about Unix Time (a.k.a Epoch time).
The RelayOperatorId, referred to in the envelope specification, is your ID in the multi-tenant PEPPOL Access Point service of Tickstar.
Schema
Find the schema for TSPeppolEnvelope.xsd here which also contains the SendResponse.
Sample Receipts
Schema documentation
Schema revision: 80eba12
Schema revision date: 2013-11-26Schema TsPeppolEnvelope.xsd
schema location: | TsPeppolEnvelope.xsd |
---|---|
attribute form default: | unqualified |
element form default: | qualified |
targetNamespace: | urn:com:tickstar:peppol:ws:envelope |
Elements | Complex types |
---|---|
SendRequest (deprecated) | ControlType |
SendResponse | DocumentIdentifierType |
StatusRequest (not in use) | ErrorType |
StatusResponse (not in use) | Extension |
TransactionRequest (deprecated) | HeaderType |
| ParticipantIdentifierType |
| ProcessIdentifierType |
| StatusType |
element SendRequest
namespace | urn:com:tickstar:peppol:ws:envelope |
---|---|
properties | content complex |
children | tns:Header tns:Data tns:Control |
annotation | documentation Request to initiate transactions towards endpoints (participants) available in the Peppol infrastructure. |
source | <xs:element name=”SendRequest”><xs:annotation><xs:documentation>Request to initiate transactions towards endpoints (participants) available in the Peppol infrastructure.</xs:documentation></xs:annotation><xs:complexType><xs:sequence><xs:elementname=”Header” type=”tns:HeaderType”/><xs:element name=”Data”><xs:complexType><xs:sequence><xs:element name=”Payload” type=”xs:base64Binary” maxOccurs=”unbounded”/></xs:sequence></xs:complexType></xs:element><xs:element name=”Control”type=”tns:ControlType” minOccurs=”0″/></xs:sequence></xs:complexType></xs:element> |
element SendRequest/Header
namespace | urn:com:tickstar:peppol:ws:envelope |
---|---|
type | tns:HeaderType |
properties | isRef: 0 content: complex |
children | tns:MessageIdentifier tns:RelayOperatorIdentifier ns:SenderIdentifier tns:RecipientIdentifier tns:DocumentIdentifier tns:ProcessIdentifier tns:InternalMessageId |
source | <xs:element name=”Header” type=”tns:HeaderType”/> |
element SendRequest/Data
namespace | urn:com:tickstar:peppol:ws:envelope |
---|---|
properties | isRef 0content complex |
children | tns:Payload |
source | <xs:element name=”Data”><xs:complexType><xs:sequence><xs:element name=”Payload” type=”xs:base64Binary” maxOccurs=”unbounded”/></xs:sequence></xs:complexType></xs:element> |
element SendRequest/Data/Payload
diagram | |
---|---|
namespace | urn:com:tickstar:peppol:ws:envelope |
type | xs:base64Binary |
properties | isRef 0minOcc 1maxOcc unboundedcontent simple |
source | <xs:element name=”Payload” type=”xs:base64Binary” maxOccurs=”unbounded”/> |
element SendRequest/Control
diagram | |
---|---|
namespace | urn:com:tickstar:peppol:ws:envelope |
type | tns:ControlType |
properties | isRef 0minOcc 0maxOcc 1content complex |
children | tns:Receivedtns:FlowIdentifiertns:Extension |
source | <xs:element name=”Control” type=”tns:ControlType” minOccurs=”0″/> |
element SendResponse
diagram | |
---|---|
namespace | urn:com:tickstar:peppol:ws:envelope |
properties | content complex |
children | tns:Status tns:Error tns:OriginalHeader tns:Control |
annotation | documentationReply from send operation. |
source | <xs:element name=”SendResponse”><xs:annotation><xs:documentation>Reply from send operation.</xs:documentation></xs:annotation><xs:complexType><xs:sequence><xs:element name=”Status” type=”tns:StatusType”/><xs:element name=”Error” type=”tns:ErrorType” minOccurs=”0″ maxOccurs=”unbounded”/><xs:element name=”OriginalHeader” type=”tns:HeaderType”/><xs:element name=”Control” type=”tns:ControlType” minOccurs=”0″/></xs:sequence></xs:complexType></xs:element> |
element SendResponse/Status
diagram | |
---|---|
namespace | urn:com:tickstar:peppol:ws:envelope |
type | tns:StatusType |
properties | isRef: 0 content: complex |
children | tns:Code tns:MessageIdentifier tns:RelayOperatorIdentifier tns:Description tns:ProofOfDelivery tns:InternalMessageId |
source | <xs:element name=”Status” type=”tns:StatusType”/> |
element SendResponse/Error
diagram | |
---|---|
namespace | urn:com:tickstar:peppol:ws:envelope |
type | tns:ErrorType |
properties | isRef 0minOcc 0maxOcc unboundedcontent complex |
children | tns:Code tns:Description tns:StackTrace tns:InModule |
source | <xs:element name=”Error” type=”tns:ErrorType” minOccurs=”0″ maxOccurs=”unbounded”/> |
element SendResponse/OriginalHeader
diagram | |
---|---|
namespace | urn:com:tickstar:peppol:ws:envelope |
type | tns:HeaderType |
properties | isRef 0content complex |
children | tns:MessageIdentifier tns:RelayOperatorIdentifier tns:SenderIdentifier tns:RecipientIdentifier tns:DocumentIdentifier tns:ProcessIdentifier tns:InternalMessageId |
source | <xs:element name=”OriginalHeader” type=”tns:HeaderType”/> |
element SendResponse/Control
diagram | |
---|---|
namespace | urn:com:tickstar:peppol:ws:envelope |
type | tns:ControlType |
properties | isRef 0minOcc 0maxOcc 1content complex |
children | tns:Received tns:FlowIdentifier tns:Extension |
source | <xs:element name=”Control” type=”tns:ControlType” minOccurs=”0″/> |
element StatusRequest
diagram | |
---|---|
namespace | urn:com:tickstar:peppol:ws:envelope |
properties | content complex |
children | tns:MessageIdentifier tns:RelayOperatorIdentifier |
annotation | documentationRequest to check current status of historic transactions. |
source | <xs:element name=”StatusRequest”><xs:annotation><xs:documentation>Request to check current status of historic transactions.</xs:documentation></xs:annotation><xs:complexType><xs:sequence><xs:element name=”MessageIdentifier” type=”xs:string”><xs:annotation><xs:documentation>A globally unique ID that uniquely will identify the transaction across multiple hops.</xs:documentation></xs:annotation></xs:element><xs:element name=”RelayOperatorIdentifier”><xs:simpleType><xs:restriction base=”xs:string”><xs:annotation><xs:documentation>Identifies relay operator. ID given by Tickstar after sign of agreement.</xs:documentation></xs:annotation><xs:minLength value=”1″/><xs:pattern value=”([0-9])*”/></xs:restriction></xs:simpleType></xs:element></xs:sequence></xs:complexType></xs:element> |
element StatusRequest/MessageIdentifier
diagram | |
---|---|
namespace | urn:com:tickstar:peppol:ws:envelope |
type | xs:string |
properties | isRef 0content simple |
annotation | documentationA globally unique ID that uniquely will identify the transaction across multiple hops. |
source | <xs:element name=”MessageIdentifier” type=”xs:string”><xs:annotation><xs:documentation>A globally unique ID that uniquely will identify the transaction across multiple hops.</xs:documentation></xs:annotation></xs:element> |
element StatusRequest/RelayOperatorIdentifier
diagram | |
---|---|
namespace | urn:com:tickstar:peppol:ws:envelope |
type | restriction of xs:string |
properties | isRef 0content simple |
facets | Kind Value annotation minLength 1 pattern ([0-9])* |
source | <xs:element name=”RelayOperatorIdentifier”><xs:simpleType><xs:restriction base=”xs:string”><xs:annotation><xs:documentation>Identifies relay operator. ID given by Tickstar after sign of agreement.</xs:documentation></xs:annotation><xs:minLength value=”1″/><xs:pattern value=”([0-9])*”/></xs:restriction></xs:simpleType></xs:element> |
- Learn more about PEPPOL in the Frequently Asked Questions section.