I have problem with adding payment method in facebook with api

LuvCii

LuvCii

Newbie
Joined
Aug 26, 2024
Messages
30
Reaction score
10
I added a payment method to my facebook account and in the body there is a data field called platform_trust_token, I don't know how to get it before sending a request to add a payment method, can any coder help me, thank you
z6764668851678_5bc83953474d39c0cfe62fd9462e35c1.jpg
 
Advertise on BHW
Careful ,anything involving platform_trust_token or payment APIs on Facebook is tightly locked and fingerprint-sensitive. That token is usually generated client-side during a legit user session and tied to browser state, device fingerprint, and Facebook’s internal risk signals.

You can’t generate it manually. It comes from a pre-authenticated session, often triggered during actual front-end interaction (usually via React events in Meta’s UI). Trying to inject a card without this token will always fail or get flagged.

If you're automating, your best bet is to simulate full browser behavior with proper session replay (or intercept token from a clean session and reuse quickly). Otherwise, Facebook will block it as suspicious.
 
FindYourHost said:
Careful ,anything involving platform_trust_token or payment APIs on Facebook is tightly locked and fingerprint-sensitive. That token is usually generated client-side during a legit user session and tied to browser state, device fingerprint, and Facebook’s internal risk signals.

You can’t generate it manually. It comes from a pre-authenticated session, often triggered during actual front-end interaction (usually via React events in Meta’s UI). Trying to inject a card without this token will always fail or get flagged.

If you're automating, your best bet is to simulate full browser behavior with proper session replay (or intercept token from a clean session and reuse quickly). Otherwise, Facebook will block it as suspicious.
Click to expand...
Thank you,
I want to know where the platform_trust_token code comes from, Do you know ?
 
LuvCii said:
Thank you,
I want to know where the platform_trust_token code comes from, Do you know ?
Click to expand...
The token doesn’t come from a fixed place ,it’s created live when a real user interacts with the payment form inside Meta’s front-end. So unless you’re actually going through the flow in a real browser session, with the right session cookies and browser fingerprint, it just won’t appear. It’s not a static value you can extract ahead of time ,it’s built on the spot. Best way to see it is to watch a real card submission in DevTools and intercept that exact request.
 
FindYourHost said:
The token doesn’t come from a fixed place ,it’s created live when a real user interacts with the payment form inside Meta’s front-end. So unless you’re actually going through the flow in a real browser session, with the right session cookies and browser fingerprint, it just won’t appear. It’s not a static value you can extract ahead of time ,it’s built on the spot. Best way to see it is to watch a real card submission in DevTools and intercept that exact request.
Click to expand...
yes i tried to intercept the request and saw it, however the next time i send the request it shows a different code, it is not fixed so when i want to get that parameter before sending the request it seems impossible
 
LuvCii said:
yes i tried to intercept the request and saw it, however the next time i send the request it shows a different code, it is not fixed so when i want to get that parameter before sending the request it seems impossible
Click to expand...
Yeah, that’s exactly the issue ,the token isn’t static, it’s regenerated every single time based on the full session context. So even if you capture it once, you can’t just reuse it later because Meta ties it to that specific browser state and moment.

If you’re trying to fetch it before the request is sent, you won’t find it in any clean form. The only way is to trigger the exact front-end interaction again ,every single time. Some people build wrappers around the actual browser session and replay the flow in real time just to catch it before it fires.
 
FindYourHost said:
Yeah, that’s exactly the issue ,the token isn’t static, it’s regenerated every single time based on the full session context. So even if you capture it once, you can’t just reuse it later because Meta ties it to that specific browser state and moment.

If you’re trying to fetch it before the request is sent, you won’t find it in any clean form. The only way is to trigger the exact front-end interaction again ,every single time. Some people build wrappers around the actual browser session and replay the flow in real time just to catch it before it fires.
Click to expand...
can you be more specific about getting it ?
 
LuvCii said:
can you be more specific about getting it ?
Click to expand...
If you’re trying to capture the platform_trust_token, the only reliable way is to let the browser generate it naturally. That means triggering the full flow in a real browser ,not skipping any step. You fill out the form exactly like a user would, then catch the request at the moment the card is submitted. DevTools “Network” tab works, or mitmproxy if you're doing it externally.

And no, you can’t predict it or pre-generate it ,it’s tied to the interaction, and expires fast. So every attempt needs its own fresh run.
 
So is there any way to fake it to make the request for the next time?
FindYourHost said:
If you’re trying to capture the platform_trust_token, the only reliable way is to let the browser generate it naturally. That means triggering the full flow in a real browser ,not skipping any step. You fill out the form exactly like a user would, then catch the request at the moment the card is submitted. DevTools “Network” tab works, or mitmproxy if you're doing it externally.

And no, you can’t predict it or pre-generate it ,it’s tied to the interaction, and expires fast. So every attempt needs its own fresh run.
Click to expand...
 
LuvCii said:
I added a payment method to my facebook account and in the body there is a data field called platform_trust_token, I don't know how to get it before sending a request to add a payment method, can any coder help me, thank youView attachment 455859
Click to expand...
I think you should not use them, it is easy to hack your computer because the origin is unclear. Please add a payment method manually or through support from Fb.
 
If you are looking for a programmer, post in the "Hire a freelancer" section.
 
Be careful with information like "platform trust token" because it is sensitive data and not public. Trying to get or use this token outside the official process can easily get your account locked or your computer infected with malware if you use unknown tools. The safest and most correct way is to add a payment method directly on the Facebook interface or ask their official support for help. Don't risk your personal security for a shortcut.
 
Facebook currently does not support additional payment methods via API for security reasons. You need to add them manually in Business Manager.
If you use API, please:
Use it for creating advertising accounts, assigning permissions, creating campaigns...
Avoid using it for payments to avoid account restrictions.
 
When adding payment on facebook. This is a security token automatically generated by facebook during the session. You need to get this token from the cookie or header in the browser when performing actual operations
 
Nproxyio said:
When adding payment on facebook. This is a security token automatically generated by facebook during the session. You need to get this token from the cookie or header in the browser when performing actual operations
Click to expand...

can you guide me ? Thank
 
That’s a common issue when using RDP or non-trusted environments. Facebook’s system is very sensitive lately.
Aged or agency accounts tend to be more stable. If you need a safer option, there are sellers offering verified setups that avoid instant suspension.
 
The `platform_trust_token` field is typically used in internal APIs or when integrating a payment method with Facebook via developer tools. To obtain this token, you need to perform a few technical steps, which typically include:

1. Log in to Business Manager as an admin.

2. Use the DevTools in your browser to monitor requests when you manually add a payment method — the token can be included in the headers or body of the relevant requests.

3. If you are a developer integrating via the Facebook Graph API or Marketing API, you will need special access or work with Facebook through an authorized partner.
 
LuvCii said:
I added a payment method to my facebook account and in the body there is a data field called platform_trust_token, I don't know how to get it before sending a request to add a payment method, can any coder help me, thank you
Click to expand...
You're likely trying to automate or reverse-engineer Facebook's internal API for adding a payment method — and yes, the platform_trust_token is part of their anti-fraud/verification system.

It’s a dynamic token generated by Meta’s frontend JS, tied to the browser fingerprint/session. It’s used to verify that a legit user is submitting the payment info.
 
A good option is to add a payment method directly on FB. Using the platform's trust token makes your account vulnerable to being locked and your computer vulnerable to viruses.
 
Advertise on BHW
You must log in or register to reply here.
Sign up now!

Main Menu

Home Main Forum List Black Hat SEO White Hat SEO BHW Newbie Guide Blogging Black Hat Tools Social Media Downloads

Marketplace

Account Selling Content / Copywriting EBooks / Methods Hosting Misc Proxies For Sale SEO - Link building SEO - Packages Social Media Social Media - Panels Web Design More

Making Money

Affiliate Programs Hire a Freelancer IM Journeys Making Money Pay Per Click Site Flipping Want to Buy

BlackHat World

Dispute Resolution Forum Suggestions & Feedback Introductions Lounge
Back
Top