Every 2nd and 16th day of the month till the end of the year: &recur_frequency=month &recur_day=2,16 &recur_until=2020-12-31
The original link could include a transaction_identifier generated by the initiator (RFC 4122 UUID?) and returned to the callback url alongside a status code? How would the direct debit confirmation work?
-
-
Not sure how you would secure the transaction confirmation though. Sign the request with the same certificate as the bank domain name and the EBA would already maintain a registry of bank domain names you can check against?
-
The best confirmation is actually receiving the funds and processing the remittance reference, and using that as the out of band verification. Instant transfers should take less than 10 seconds and most of them are under 5, which might be an acceptable wait time
End of conversation
New conversation -
-
-
It could, but then you're reliant on the callback, which many don't even reach. If 5-10 sec is guaranteed, then yes: using receiving of the funds would be best. Currently instant payments is a no-go for businesses, but that needs to change.
-
What do you mean by “don’t even reach”? And why is it currently a “no-go for businesses”?
End of conversation
New conversation -
-
-
Direct Debit would work similar: pay.europa.eu/v2/ ?type=sdd &receiver_name=Some+Company &receiver_identifier=NL91ABNA0417164300 Set repeat params for subscriptions. Callback URL should be trigger upon confirmation including mandateID, IBAN and maybe name.
-
Directly verifies you as the owner. Different chargeback rules should apply.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
at
retweets