Stripe-to-Elorus Receipt Issuance Automation
Budget: €250 – €750 EUR
My Stripe account collects payments for my laundry services (wash & dry). Elorus, the Greek accounting platform I use, already offers a built-in Stripe link for the opposite workflow—creating a charge after I issue a receipt—but I need things reversed: every time Stripe confirms a payment, Elorus must immediately receive the details and generate the legally compliant receipt on its side.
Here’s what matters:
• Trigger: Stripe’s successful payment_intent webhook (or an equally reliable event).
• Action: Call Elorus’s public API to create a new receipt.
• Mandatory data on the receipt: the exact payment amount, VAT and the short service description coming from the Stripe metadata you help me define.
• Service category: all payments will be tagged as Laundry Services in Elorus.
I’ll provide live API keys and test accounts. Your solution can be a lightweight serverless function, a small Node/Python service, or an integration inside a workflow tool—whichever you find most robust and maintainable. Just make sure it:
1. Handles retries so no receipt is lost if either side is momentarily down.
2. Prevents duplicates when Stripe sends the same event twice.
3. Logs each call for easy troubleshooting.
Once it’s running in production and I see a receipt pop up in Elorus right after a real Stripe payment, the job is done.
Here’s what matters:
• Trigger: Stripe’s successful payment_intent webhook (or an equally reliable event).
• Action: Call Elorus’s public API to create a new receipt.
• Mandatory data on the receipt: the exact payment amount, VAT and the short service description coming from the Stripe metadata you help me define.
• Service category: all payments will be tagged as Laundry Services in Elorus.
I’ll provide live API keys and test accounts. Your solution can be a lightweight serverless function, a small Node/Python service, or an integration inside a workflow tool—whichever you find most robust and maintainable. Just make sure it:
1. Handles retries so no receipt is lost if either side is momentarily down.
2. Prevents duplicates when Stripe sends the same event twice.
3. Logs each call for easy troubleshooting.
Once it’s running in production and I see a receipt pop up in Elorus right after a real Stripe payment, the job is done.
Related categories:
PHP
JavaScript
Python
Software Architecture
Node.js
Software Development
Stripe
Automation
API Integration
Payment Processing