Menu

Telr payments in ASP.NET Core: the parts the docs skip
📰

Telr payments in ASP.NET Core: the parts the docs skip

DEV Community: dotnet·Anas Amin·13 days ago
#AuSMyxVm
#devtodotnet#devto#dev#order#telr
Reading 0:00
15s threshold

Telr’s hosted payment page takes an afternoon to wire up. The real work is everything around it: the redirect that never comes back, the callback that arrives twice, and the payment that lands after you already released the seats.

Three signals, one of them trustworthy

With a hosted payment page your API never touches the card. You create an order at Telr, send the customer to the page it returns, and wait to hear how it went. You hear it three ways, and they are not equal.

The return URL. The browser comes back to your authorised, declined or cancelled page. Useful for the user, worthless as proof: anyone can type that URL, and a closed tab never arrives at all.

The callback. Telr posts a signed, form-encoded advice to your server (ivp_update_url). Good evidence once you check the signature, but it can arrive late, twice, or before the browser does.

order/check. Your server asks Telr about the order by its reference.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.