Technical Documentation needed (PHP): Retrieve transaction and order data from Amazon APIs

ATTENTION: Please note that generic applications will not be considered. Any application that does not in detail refer to the project description will be disregarded. The Project Scope We are in search of an Amazon API expert who can WRITE US A TECHNICAL DOCUMENTATION on how to retrieve the below specified payment and order data from Amazons APIs. With this documentation we are aiming to build a microservice by ourselves that aggregates this data from Amazon APIs for any given Amazon seller who provides us with his Amazon authentication credentials. This Microservice should then import the required data via our API. Within a second consecutive project the service provider (you) could potentially also develop this microservice and its integration for us, depending how the first project will go. Anyhow, this is not part of the current project. About us We develop a German cloud-based accounting software that integrates with banks and payment service providers on one side and imports invoices from invoicing tools on the other side. Our software matches invoices and transactions and generates accounting records that the user can simply confirm with one click. Development (potential second project – not part of this project) The microservice shall preferably be developed in PHP. The code has to be checked in using Bitbucket. Your Profile You have extensive experience with the Development of PHP applications and you already worked with Amazon APIs. Your English Level is C1. You have vast experience with writing technical documentations for developers. The Task You write a detailed description of all necessary steps that are required to retrieve the below mentioned data from Amazon Pay API, AWS API and/or MWS API. The description has to enable us to code the solution ourselves with a minimum of effort. The user shall enter his Amazon API Credentials and an “import since” date. The following data has to be aggregated from Amazon Pay API The following list gives an overview of the mandatory values. All values that can be captured in addition should be aggregated as well. • Date and time of the transaction • Settlement ID • Amazon Transaction ID • Amazon Order Reference • Transaction type • Amount • Currency • Transaction fees (fixed) • Transaction fees (percentage) This data has to be enriched with additional, order specific information that can be retrieved from Amazon API (AWS and/or MWS) • Buyer name • Buyer address • Buyer country • Buyer Company name (if applicable) • Buyer VAT-ID (if applicable) • Shipment to country (if different from buyer country) • Shipment from country (only relevant for Amazon FBA sellers) • Order information (article, price) • Information on VAT if available (VAT applicable vs. Reverse-Charge VAT procedure for B2B shipments within the EU) All relevant values that can be further retrieved from Amazon regarding an order should be retrieved on top. Challenges and Questions --> Order data for “normal” Amazon sellers and for Amazon FBA sellers (Fulfillment by Amazon) might have to be retrieved using different API end points --> If the status of a transaction changes, e.i. because a customer gets a full or partial refund, we would need this data as a new transaction with the timestamp of the moment the refund occurred Deliverables - You provide us with a detailed technical documentation how to develop such microservice - You guide us through the documentation and explain all steps in detail