Skip to main content
Every commerce integration begins the same way: represent your user, verify their identity, and discover their credit cards. For commerce, the primary goal is connecting the user’s credit cards for linking, transactions, or tokenization.
1

Create an Entity

Every end user maps to an Entity in Method. Create one with the user’s identifying information. This is the foundational object that verification, card discovery, and all downstream products attach to.
The Entity is created in incomplete status. Before you can discover Emily’s credit cards, you need to verify her identity.
2

Verify Identity

Method requires phone verification before card discovery. Initiate an SMS verification session — this sends a one-time code to Emily’s phone number on record.
After Emily receives and submits the SMS code, the verification session transitions to verified. Once both phone and identity verification are complete, the Entity status updates to active and Connect becomes available.
For a complete overview of all verification methods (SMS, SNA, BYO-SMS, KBA), see the Identity Verification guide.
3

Connect Credit Cards

With verification complete, call Connect to discover Emily’s credit cards via a soft-pull credit report. This has no impact on the user’s credit score.For commerce use cases, the key discovery is credit cards — these are the accounts you’ll use for card linking, brand enrichment, transaction streaming, and tokenization.
Method discovered 4 credit card accounts for Emily:These accounts are now ready for card brand enrichment and payment instrument tokenization.

What’s Next

Card Linking & Checkout

Enrich cards with brand art, tokenize for checkout, and create card-on-file instruments.