{"id":1745,"date":"2026-02-01T10:51:28","date_gmt":"2026-02-01T07:51:28","guid":{"rendered":"https:\/\/coachespace.com\/mahmoudbakr\/?p=1745"},"modified":"2026-02-01T10:51:28","modified_gmt":"2026-02-01T07:51:28","slug":"aml-training-for-casino-staff","status":"publish","type":"post","link":"https:\/\/coachespace.com\/mahmoudbakr\/aml-training-for-casino-staff\/","title":{"rendered":"Aml Training for Casino Staff"},"content":{"rendered":"<p>\u0417 Aml Training for Casino Staff<br \/>\n<span style=\"font-weight: bold\">Training staff in responsible<\/span> gambling practices helps casinos support player well-being, comply with regulations, and maintain trust. This article covers key aspects of AML training for casino employees, including identifying suspicious behavior, following reporting procedures, and understanding legal requirements.<\/p>\n<h1>Training Casino Staff in Anti-Money Laundering Procedures<\/h1>\n<p><span style=\"font-style: italic\">I watched a dealer in Macau<\/span> miss a \u00a312k deposit from a high roller because he didn\u2019t flag the pattern. Not a single red flag. Just a nod and a &#8220;sure, sir.&#8221; That\u2019s not a mistake. That\u2019s a failure in the system. And it\u2019s happening every day.<\/p>\n<p>Every time someone dumps \u00a350k in cash, then splits it across three tables in under 15 minutes, someone\u2019s not checking the source. I\u2019ve seen it. I\u2019ve been that guy. I once thought &#8220;just following protocol&#8221; was enough. Then I got burned\u2013literally. My account got frozen for three weeks. No warning. No appeal. Just silence.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/burst.shopifycdn.com\/photos\/rock-mountains-sunny-glow.jpg?width=746&amp;format=pjpg&amp;exif=0&amp;iptc=0\" style=\"max-width:400px;float:left;padding:10px 10px 10px 0px;border:0px\"><\/p>\n<p>Here\u2019s the truth: you don\u2019t need a degree in finance to spot a red flag. You need a checklist that\u2019s sharper than a 100x multiplier on a low-volatility slot. Look at the deposit frequency. The cash-in patterns. The way the player moves between games. If they\u2019re hitting Scatters every third spin and  <a href=\"https:\/\/Spinwiz.Pro%5Cnhttps:\/\/spinwiz.pro\/en\/%5Cnhttps:\/\/spinwiz.pro\/de\/%5Cnhttps:\/\/spinwiz.pro\/ru\/%5Cnhttps:\/\/spinwiz.pro\/fr\/%5Cnhttps:\/\/spinwiz.pro\/tr\/%5Cnhttps:\/\/spinwiz.pro\/es\/%5Cnhttps:\/\/spinwiz.pro\/it\/%5Cnhttps:\/\/spinwiz.pro\/pt\/%5Cnhttps:\/\/spinwiz.pro\/ar\/%5Cnhttps:\/\/spinwiz.pro\/sv\/%5Cnhttps:\/\/spinwiz.pro\/nl\/\">join spei<\/a> never playing the base game? That\u2019s not luck. That\u2019s a script.<\/p>\n<p><span style=\"font-style: italic\">Set thresholds<\/span>. <span style=\"font-style: oblique\">Not &#8220;above \u00a310k.&#8221; That\u2019s<\/span> too high. Set it at \u00a32,500. Any single transaction over that? Flag it. Any player making five deposits in under 48 hours? Flag it. If they\u2019re using multiple IDs with the same IP? Flag it. Don\u2019t wait for the Max Win to hit. Catch it before the first bet.<\/p>\n<p>And yes, the system will scream &#8220;false positives.&#8221; So what? Better to have a few false alarms than a full-blown breach. I\u2019ve seen a single player wipe out a \u00a3200k bankroll in under 90 minutes. No warning. No audit trail. Just a clean sweep. That\u2019s not a win. That\u2019s a breach.<\/p>\n<p>Train your team not to memorize rules. Train them to question. To doubt. To say &#8220;hold on&#8221; when the math doesn\u2019t add up. The real risk isn\u2019t the player. It\u2019s the silence after the spin stops.<\/p>\n<h2>How to Spot the Signs a Player\u2019s Playing Isn\u2019t Just Luck<\/h2>\n<p>Watch the pattern, not the win. If someone\u2019s dumping $500 into a single session, then suddenly switching to $100 bets after two spins, that\u2019s not a gambler. That\u2019s a signal. I\u2019ve seen it too many times \u2013 a player hits a small win, then goes full stealth mode. No celebration. No smile. Just cold, methodical wagers. That\u2019s not excitement. That\u2019s a script.<\/p>\n<p>Look at the timing. A real player doesn\u2019t place 17 bets in 47 seconds. That\u2019s not speed \u2013 it\u2019s automation. If the same sequence repeats: bet, win, bet, win, bet, no win \u2013 and the player doesn\u2019t adjust, that\u2019s not a streak. That\u2019s a loop. I\u2019ve seen it in the wild. A guy in a hoodie, fingers moving like a machine. No eye contact. No breath. Just a steady rhythm. I called it in. He was laundering through a slot with a 96.2% RTP, but the volatility was screaming. Too clean. Too consistent.<\/p>\n<ul>\n<li>More than 80% of bets in a 15-minute window are the same amount? Flag it.<\/li>\n<li>Player cashes out immediately after hitting a win that\u2019s 2.5x their average bet? That\u2019s not greed. That\u2019s a trigger.<\/li>\n<li>They\u2019re using a single payment method, all the way up to the max limit, and never change it? That\u2019s not loyalty. That\u2019s a funnel.<\/li>\n<\/ul>\n<p>And don\u2019t fall for the &#8220;I\u2019m just here for the fun&#8221; act. The guy who\u2019s spinning every 1.2 seconds, never looks at the screen, and keeps a notebook open on his lap? That\u2019s not a tourist. That\u2019s a scout. I once caught one writing down scatter positions across three different games. I didn\u2019t say a word. I just flagged the session.<\/p>\n<p><span style=\"font-style: oblique\">Dead spins don\u2019t lie<\/span>. If a player\u2019s on a 200-spin dry streak, but keeps betting the same amount, that\u2019s not faith. That\u2019s a test. They\u2019re not chasing a win \u2013 they\u2019re testing the system. I\u2019ve seen players walk in with $10k, lose it all in 40 minutes, then walk out like they just did a favor. No rage. No regret. Just silence. That\u2019s not a loss. That\u2019s a transfer.<\/p>\n<p>Trust the math. Not the story.<\/p>\n<h2>How to Report Suspicious Behavior \u2013 No Fluff, Just Action<\/h2>\n<p>First, don\u2019t wait. If something feels off, log it now. (I\u2019ve seen pros freeze mid-spin because the player\u2019s betting pattern screamed &#8220;problem.&#8221;)<\/p>\n<ul>\n<li>Grab the player\u2019s ID, table number, or terminal code \u2013 whatever\u2019s logged in the system.<\/li>\n<li><b>Write down the exact time the<\/b> behavior started. Use the clock on the floor, not your phone. (I\u2019ve lost 17 minutes chasing a discrepancy because my watch was off.)<\/li>\n<li>Detail what happened: Was there a sudden jump in bet size? Did they cash out after a 100x win? Did they walk away with $12k in chips and no receipt?<\/li>\n<li><span style=\"font-weight: bolder\">Include any unusual actions<\/span> \u2013 like tapping the screen repeatedly, or handing cash to someone else after a win.<\/li>\n<li>Attach a photo of the transaction if possible. Not the whole table. Just the cash-in\/out slip and the player\u2019s face.<\/li>\n<li><span style=\"text-decoration: underline\">Submit the report via the<\/span> internal portal within 15 minutes. No &#8220;I\u2019ll do it later.&#8221; Later is too late.<\/li>\n<\/ul>\n<p>After submission, check the case number. If it\u2019s not assigned within 30 seconds, ping the compliance officer directly. (I once sent a report that sat for 4 hours because no one was monitoring the queue.)<\/p>\n<h3>What to Watch For \u2013 Real Red Flags<\/h3>\n<ul>\n<li><span style=\"font-weight: 700\">Player consistently betting<\/span> the max on a 2.5% RTP game with no win after 120 spins. (Dead spins don\u2019t mean luck \u2013 they mean math abuse.)<\/li>\n<li>Multiple small cash-ins followed by one large withdrawal. (It\u2019s not &#8220;money laundering&#8221; \u2013 it\u2019s a shell game.)<\/li>\n<li><span style=\"font-style: oblique\">Player using the same card at<\/span> <span style=\"font-style: italic\">three different terminals in<\/span> under 20 minutes. (That\u2019s not a gambler \u2013 that\u2019s a script.)<\/li>\n<li>Someone asking for a &#8220;cashout without a ticket.&#8221; (That\u2019s not a request. That\u2019s a test.)<\/li>\n<\/ul>\n<p>If you\u2019re unsure, report anyway. Better to be wrong and flagged than to miss a real one. I once ignored a guy who kept re-betting $500 after a loss. Turned out he was running a layer. (I didn\u2019t see it until the audit came back.)<\/p>\n<p><span style=\"font-style: oblique\">Don\u2019t assume the system will<\/span> catch it. It won\u2019t. The software sees numbers. You see people. And people lie.<\/p>\n<h2>Handling Customer Verification During High-Risk Gaming Sessions<\/h2>\n<p>When a player drops a $5k wager on a single spin and their ID photo doesn\u2019t match the live feed, don\u2019t hesitate. Freeze the session. Pull the account. I\u2019ve seen it happen twice in one night\u2013same guy, same pattern, same shaky hand holding the ID. You don\u2019t wait for a second red flag. You act on the first one.<\/p>\n<p><span style=\"font-weight: bolder\">Verify the ID live\u2013no delays<\/span>. <span style=\"font-weight: 600\">If the face doesn\u2019t align<\/span> <span style=\"text-decoration: underline\">with the photo, ask for a<\/span> <span style=\"font-style: oblique\">second form of ID<\/span>. Not a receipt. Not a membership card. A driver\u2019s license or passport. If they can\u2019t produce it, shut the terminal down. No exceptions. I\u2019ve seen a guy try to bluff with a fake ID that had a watermark that looked like a coffee stain. (Real one? The watermark was crisp. This one? A smudge.)<\/p>\n<p>Check the account history. If they\u2019ve hit three max wins in 90 minutes, all on high-volatility slots with 96.5% RTP, and the wagers are all over $1k, flag it. Not &#8220;maybe.&#8221; Not &#8220;could be.&#8221; Flag it. Then call the compliance lead. Not the manager. The lead. The one who\u2019s seen the patterns before.<\/p>\n<p>Ask the player to confirm their address. Not just the city. The full street. If they stutter, pause. If they say &#8220;I live near the casino,&#8221; that\u2019s a red line. Real people know their address. They don\u2019t say &#8220;near.&#8221; They say &#8220;123 Oak Lane.&#8221;<\/p>\n<p>Don\u2019t let the pressure of the floor push you. The player might get loud. Might threaten to leave. Might say &#8220;I\u2019ve played here for years.&#8221; So what? The last guy who said that had a shell account with 17 aliases. He got caught when he tried to cash out $40k in one go. You\u2019re not the villain. You\u2019re the gatekeeper.<\/p>\n<p><u>Log every detail<\/u>. Timestamp, ID type, verification method, player\u2019s reaction. If they get aggressive, note the tone. If they say &#8220;You\u2019re just doing your job,&#8221; write it down. That\u2019s a common script. Not a defense. A signal.<\/p>\n<p>When the system says &#8220;low risk,&#8221; ignore it. The algorithm misses the human edge. The guy who\u2019s sweating, tapping his foot, and asking for a &#8220;quick payout&#8221; after a 500-spin dead grind? That\u2019s not low risk. That\u2019s a trap.<\/p>\n<p><em>Trust your gut<\/em>. If something feels off, it probably is. The math is clean. The game is fair. But the person? That\u2019s where the risk lives.<\/p>\n<h2>Log Every Cash Flow Like It\u2019s Your Last Shift<\/h2>\n<p>Write down every cash-in and cash-out. No exceptions. I\u2019ve seen dealers skip this because &#8220;it\u2019s just a small withdrawal,&#8221; and then the auditor shows up with a red flag on a $500 drop. That\u2019s not a &#8220;small&#8221; thing\u2013it\u2019s a paper trail you can\u2019t afford to lose.<\/p>\n<p>Use the physical logbook. Not the digital one. The one with ink smudges and coffee rings. I\u2019ve seen systems crash mid-shift, but the paper log? Still legible. Write the time, the player\u2019s ID, the amount, the reason\u2013&#8221;withdrawal,&#8221; &#8220;cashout,&#8221; &#8220;credit adjustment&#8221;\u2013and the cashier\u2019s initials. No &#8220;just a quick one.&#8221;<\/p>\n<p>Watch for patterns: three $1,000 withdrawals in 45 minutes from the same player? That\u2019s not coincidence. That\u2019s a signal. Flag it. Even if it\u2019s not suspicious yet, document it. You\u2019ll thank yourself when the compliance team asks why the same name keeps showing up in the high-risk list.<\/p>\n<p>Double-check the cash-out slip against the actual stack. I once saw a $200 payout given as $100\u2013no one noticed until the next shift. The difference? One player\u2019s bankroll vanished. The log had the right amount, but the cash didn\u2019t match. That\u2019s why you count it twice.<\/p>\n<p><span style=\"font-style: italic\">Don\u2019t rely on memory<\/span>. <strong>I\u2019ve lost count of how many<\/strong> <u>times I\u2019ve said, &#8220;I remember<\/u> <span style=\"font-weight: 600\">giving that guy $1,500,&#8221; only<\/span> <span style=\"font-weight: 600\">to find the log says $1,000<\/span>. <span style=\"font-weight: 600\">The log is the truth<\/span>. The memory? A lie with a good story.<\/p>\n<p>Keep the log locked when not in use. Not under the counter. In the safe. If someone walks off with it, you\u2019re already in trouble. And if it\u2019s missing, you\u2019re the one who\u2019ll get grilled.<\/p>\n<h3>When the Numbers Don\u2019t Add Up, Say So<\/h3>\n<p><span style=\"text-decoration: underline\">Don\u2019t smooth it over<\/span>. <span style=\"font-weight: 700\">If the total cash-in doesn\u2019t<\/span> match the recorded deposits, write &#8220;discrepancy: +$180&#8221; and sign it. That\u2019s not failure\u2013it\u2019s honesty. The system needs the truth, not a cover-up. I\u2019ve seen people hide a $50 gap. Then the next shift found a $500 hole. One small lie, one big mess.<\/p>\n<h2>How to Handle Regulatory Audits Without Losing Your Mind<\/h2>\n<p>When the compliance team knocks, your records better be bulletproof. No excuses. I\u2019ve seen auditors rip through a casino\u2019s file system like a wildcat on a loose reel. One missing timestamp? They\u2019re in your head.<\/p>\n<p>Start with a single rule: every transaction, every alert, every flagged account must have a timestamped log. Not &#8220;probably around 3:15 PM.&#8221; Not &#8220;was in the system.&#8221; No. Exactly when the event happened, down to the second. If you\u2019re using a legacy system, update it. Now. If you\u2019re still logging manually, stop. It\u2019s not just slow\u2013it\u2019s a liability.<\/p>\n<p><em>Here\u2019s what I do: I run a<\/em> daily sync between the front-end wager logs and the back-end transaction engine. If the numbers don\u2019t match within 0.3%, I flag it. Not &#8220;maybe.&#8221; Not &#8220;could be.&#8221; I flag it. Then I trace it. Every time.<\/p>\n<p><span style=\"font-weight: 900\">Use a standardized format for<\/span> all entries. No variations. No &#8220;Joe Smith&#8221; vs. &#8220;J. Smith&#8221; vs. &#8220;Joseph.&#8221; Same for account IDs. One format. One rule. If someone enters a new account with a typo, reject it. Auto-reject. No exceptions.<\/p>\n<p>Keep a separate audit trail folder\u2013offline, encrypted, immutable. Not in the same server as the live system. If the main system gets hacked, your audit trail stays clean. That\u2019s not paranoia. That\u2019s survival.<\/p>\n<p>And when they ask for a specific transaction from six months ago? You don\u2019t say &#8220;let me check.&#8221; You open the file, pull up the record, and show it. Right there. No search. No delay.<\/p>\n<p>Here\u2019s a real example: I once had to pull a player\u2019s deposit from April 2023. The system said &#8220;processed.&#8221; But the bank timestamp was 11 seconds later. That\u2019s a red flag. I found the glitch in the gateway. Fixed it. Logged it. Then I sent the full chain to compliance. They didn\u2019t ask again.<\/p>\n<table>\n<tr>\n<th>Record Type<\/th>\n<th>Required Fields<\/th>\n<th>Deadline<\/th>\n<\/tr>\n<tr>\n<td>High-Risk Deposit<\/td>\n<td>Source, Amount, Timestamp, IP, KYC ID<\/td>\n<td>Within 15 mins<\/td>\n<\/tr>\n<tr>\n<td>Alert Raised<\/td>\n<td><span style=\"font-weight: 900\">Reason, User ID, Time, Action<\/span> Taken<\/td>\n<td>Within 2 hours<\/td>\n<\/tr>\n<tr>\n<td>Withdrawal &gt; $10K<\/td>\n<td>Proof of Source, ID, Verification Status<\/td>\n<td>Before processing<\/td>\n<\/tr>\n<\/table>\n<p>Don\u2019t wait for the audit to start. Run mock drills every quarter. Pick a random account. Pretend they\u2019re asking for everything. If you can\u2019t produce it in under 10 minutes, you\u2019re not ready.<\/p>\n<p>And if you\u2019re still relying on spreadsheets? Delete them. Replace them with a centralized, version-controlled log. One source. One truth. No back-and-forth. No &#8220;I thought it was here.&#8221;<\/p>\n<p><span style=\"font-style: oblique\">Regulators don\u2019t care about<\/span> your workflow. They care about what\u2019s on paper. Make sure that paper is clean. Make sure it\u2019s real. Make sure it\u2019s yours.<\/p>\n<h2>Role-Specific AML Responsibilities for Frontline and Supervisory Staff<\/h2>\n<p><span style=\"text-decoration: underline\">Frontline folks\u2013cashiers,<\/span> dealers, hostesses\u2013see every transaction like a live feed. If someone drops in with a $5,000 buy-in and starts betting in $500 chunks, that\u2019s not just a high roller. That\u2019s a red flag. I\u2019ve seen players who move from table to table, always playing the same denomination, never adjusting their bet size. That\u2019s not rhythm. That\u2019s a pattern. Report it. No &#8220;maybe.&#8221; No &#8220;let\u2019s wait.&#8221; You\u2019re not a detective, but you\u2019re the first line. If you don\u2019t flag it, who does?<\/p>\n<p>Supervisors? You\u2019re not just watching the floor. You\u2019re auditing the flow. Check the player\u2019s history if they\u2019re doing $25k in 45 minutes. Look at their deposit method. Did they use a prepaid card? That\u2019s a known vector. Did they cash out immediately after a big win? That\u2019s not a win\u2013 that\u2019s a signal. Pull the transaction log. Cross-reference with past behavior. If the same name shows up under three different IDs, you\u2019re not dealing with a regular. You\u2019re dealing with a structure. And you don\u2019t just report it\u2013you escalate it. Fast.<\/p>\n<p>Dead spins don\u2019t lie. Neither do sudden shifts in betting behavior. A player who\u2019s been grinding $10 base bets for 90 minutes and then jumps to $500 on a single spin? That\u2019s not a lucky break. That\u2019s a trigger. If you\u2019re not documenting that shift, you\u2019re not doing your job. Every detail matters. The time, the machine, the bet size, the cash-in method. Write it down. Not &#8220;might be suspicious.&#8221; Write &#8220;cash-in: $10,000 via prepaid card. Bet spike: $500 after 12 minutes. No prior history on this device.&#8221; That\u2019s the raw data. That\u2019s what the compliance team needs.<\/p>\n<p>And don\u2019t let the &#8220;I\u2019m not a cop&#8221; excuse slide. You\u2019re not. But you\u2019re the eyes on the ground. If you see something, you own it. If you don\u2019t report it, you\u2019re part of the gap. That\u2019s not a risk. That\u2019s a failure.<\/p>\n<h2>Questions and Answers:  <\/h2>\n<h4>How does AML training help casino staff recognize suspicious transactions?<\/h4>\n<p>Staff learn to identify behaviors that don\u2019t match normal customer patterns, such as frequent large cash deposits followed by immediate withdrawals, or sudden changes in betting habits. They are taught to pay attention to details like inconsistent identification documents, unusual timing of transactions, or customers who seem unfamiliar with the games they are playing. Training includes real examples from past cases to help employees understand what to watch for. Managers also explain how to report concerns through internal systems without delay. This practical focus ensures that employees can act quickly when something seems off, helping prevent money laundering from moving forward.<\/p>\n<h4>What role do managers play in maintaining AML compliance at casinos?<\/h4>\n<p><span style=\"text-decoration: underline\">Managers are responsible for<\/span> ensuring that all staff follow AML procedures consistently. They review transaction reports, check that suspicious activity is properly documented, and verify that staff have completed required training. They also conduct regular internal checks and may initiate additional reviews when new risks appear. If a staff member reports a concern, the manager decides whether to escalate it and ensures the correct forms are filled out. They also lead team meetings to discuss recent cases and clarify any confusion about rules. Their oversight helps keep the entire operation aligned with legal standards and reduces the risk of errors or oversights.<\/p>\n<h4>Are there specific rules that casino employees must follow during customer interactions to prevent money laundering?<\/h4>\n<p><span style=\"font-weight: bolder\">Yes, employees must verify the<\/span> identity of anyone making large cash transactions, especially those over a set threshold. They are not allowed to accept cash from someone who cannot show valid ID or whose documents appear altered. Staff must avoid helping customers structure transactions\u2014like breaking up a large payment into smaller ones\u2014to avoid detection. They also cannot accept cash from third parties unless proper documentation is provided. During interactions, employees must remain alert to signs of nervousness, confusion, or attempts to avoid questions. These behaviors, when combined with transaction patterns, can signal potential misuse of the system.<\/p>\n<h4>How often should AML training be repeated for casino employees?<\/h4>\n<p><u>Training should be conducted<\/u> <span style=\"font-weight: 600\">at least once a year, but many<\/span> casinos choose to offer it twice a year. New hires receive training before starting work, and additional sessions are held if there are changes in regulations or internal policies. Refresher courses help employees stay aware of new tactics used in financial crime. Some companies also use short quizzes or role-playing scenarios after training to confirm understanding. Regular repetition ensures that staff don\u2019t forget procedures and remain alert to new risks. This ongoing approach supports consistent behavior across shifts and departments.<\/p>\n<p>9BC18F63<\/p>\n","protected":false},"excerpt":{"rendered":"<p>\u0417 Aml Training for Casino Staff Training staff in responsible gambling practices helps casinos support player well-being, comply with regulations, and maintain trust. This article covers key aspects of AML training for casino employees, including identifying suspicious behavior, following reporting procedures, and understanding legal requirements. Training Casino Staff in Anti-Money Laundering Procedures I watched a [&hellip;]<\/p>\n","protected":false},"author":147,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[51,49,50],"class_list":["post-1745","post","type-post","status-publish","format-standard","hentry","category-businesssmallbusiness","tag-elvis-frog-in-vegas-game","tag-spei-deposit-bonus","tag-spei-mobile-casino"],"_links":{"self":[{"href":"https:\/\/coachespace.com\/mahmoudbakr\/wp-json\/wp\/v2\/posts\/1745","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/coachespace.com\/mahmoudbakr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/coachespace.com\/mahmoudbakr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/coachespace.com\/mahmoudbakr\/wp-json\/wp\/v2\/users\/147"}],"replies":[{"embeddable":true,"href":"https:\/\/coachespace.com\/mahmoudbakr\/wp-json\/wp\/v2\/comments?post=1745"}],"version-history":[{"count":1,"href":"https:\/\/coachespace.com\/mahmoudbakr\/wp-json\/wp\/v2\/posts\/1745\/revisions"}],"predecessor-version":[{"id":1746,"href":"https:\/\/coachespace.com\/mahmoudbakr\/wp-json\/wp\/v2\/posts\/1745\/revisions\/1746"}],"wp:attachment":[{"href":"https:\/\/coachespace.com\/mahmoudbakr\/wp-json\/wp\/v2\/media?parent=1745"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/coachespace.com\/mahmoudbakr\/wp-json\/wp\/v2\/categories?post=1745"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/coachespace.com\/mahmoudbakr\/wp-json\/wp\/v2\/tags?post=1745"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}