He landed in Salvador, checked into a pousada, and bought a fresh coconut from a beach vendor. The card worked perfectly.

Strange, but maybe a temporary glitch. He tried another ATM. Same message. Then his phone buzzed — an SMS from Santander: “Suspicious activity detected. Your card has been temporarily blocked. Please call us.” Diego wasn’t overly worried. He had roaming data, so he called the UK fraud team via Skype. After 20 minutes on hold, an agent confirmed: “We saw two failed ATM attempts in Brazil. That triggered our system. I’ve unblocked your card now.”

He needed to withdraw Brazilian reais to pay his hostel in cash (as they didn’t accept cards). He found a Banco24Horas ATM, inserted his Santander card, and requested 600 BRL. The machine hummed, then displayed: “Transaction declined. Contact your bank.”

Santander’s fraud team admitted the block was correct — his card was compromised. But to unblock it and issue a replacement, he had to visit a branch in person with ID. In Brazil. There are no Santander branches in Brazil that service UK accounts. He was stuck.

Santander had blocked his card to protect him from fraud — but their rigid “branch-only” verification policy for unblocking left a digital nomad effectively cashless abroad. He later tweeted about it, and the tweet went viral with the hashtag #SantanderBlockedMeInBrazil . Within 48 hours, Santander’s social media team DM’d him, apologized, and credited his account £75 for the phone calls.

Diego opened the app. There it was — a toggle he’d never noticed: “I am traveling and confirm these transactions.” He’d missed it because the app’s UI had changed two days before his flight.

Santander Block Card !full! -

He landed in Salvador, checked into a pousada, and bought a fresh coconut from a beach vendor. The card worked perfectly.

Strange, but maybe a temporary glitch. He tried another ATM. Same message. Then his phone buzzed — an SMS from Santander: “Suspicious activity detected. Your card has been temporarily blocked. Please call us.” Diego wasn’t overly worried. He had roaming data, so he called the UK fraud team via Skype. After 20 minutes on hold, an agent confirmed: “We saw two failed ATM attempts in Brazil. That triggered our system. I’ve unblocked your card now.” santander block card

He needed to withdraw Brazilian reais to pay his hostel in cash (as they didn’t accept cards). He found a Banco24Horas ATM, inserted his Santander card, and requested 600 BRL. The machine hummed, then displayed: “Transaction declined. Contact your bank.” He landed in Salvador, checked into a pousada,

Santander’s fraud team admitted the block was correct — his card was compromised. But to unblock it and issue a replacement, he had to visit a branch in person with ID. In Brazil. There are no Santander branches in Brazil that service UK accounts. He was stuck. He tried another ATM

Santander had blocked his card to protect him from fraud — but their rigid “branch-only” verification policy for unblocking left a digital nomad effectively cashless abroad. He later tweeted about it, and the tweet went viral with the hashtag #SantanderBlockedMeInBrazil . Within 48 hours, Santander’s social media team DM’d him, apologized, and credited his account £75 for the phone calls.

Diego opened the app. There it was — a toggle he’d never noticed: “I am traveling and confirm these transactions.” He’d missed it because the app’s UI had changed two days before his flight.

img#pf-header-img { width:40% !important; margin-top:10px !important; margin-bottom:20px; margin-left:0 !important; } #pf-content > div:nth-child(1) > div > div > div.et_pb_module.et_pb_post_content.et_pb_post_content_0_tb_body > div > div > div > div > div > div > div.et_pb_button_module_wrapper.et_pb_button_0_wrapper.et_pb_module > a {background-color:#F2330E; border-radius:50px; padding:10px; padding-left:30px; padding-right:30px; font-weight:bold;color:#fff; margin-bottom:50px !important;text-decoration:none !important;} h1 {font-size: 40px !important; margin-top:15px !important; margin-bottom: !important; padding-bottom:5px !important;}