Skip to main content
Use this page when you are replacing a legacy browser card flow.

​
What changes

  • raw browser tokenization flow -> hosted Payment Element field
  • legacy browser-side card orchestration -> elements.submit(...)
  • custom challenge plumbing -> next_action driven flow
  • unstable browser contract -> stable backend POST /v2/transactions

​
Keep stable during migration

  • keep your backend transaction route stable
  • keep external_ref, transaction ID, and requestId persistence unchanged
  • keep webhook and reconciliation logic unchanged
  • migrate one checkout surface at a time

​
Backend contract example

{
  "external_ref": "order_2001",
  "amount": 2490,
  "currency": "BRL",
  "method": "credit_card",
  "token": "pgct_token_from_browser"
}