feat(BTI-17): add PayPerEmail example and feature test#12
Merged
Conversation
- add examples/payperemail.py demoing the PaymentInvitation flow, creds-gated like examples/in3.py - add feature test asserting the PaymentInvitation action and customer service params reach the wire
DjellzeBllaca
approved these changes
Jul 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Brings PayPerEmail to parity with peer payment methods (e.g. in3). The builder and unit tests already exist on
develop; this adds the two missing pieces.examples/payperemail.py— demos thePaymentInvitationflow, creds-gated likeexamples/in3.py.tests/feature/payments/test_payperemail.py— asserts thePaymentInvitationaction and customer service params (email, first/last name, gender) reach the wire.Why
Jira BTI-17 asked to "add solution: PayPerEmail". In this SDK PayPerEmail is correctly a payment method (
PaymentInvitationposts to/json/transaction), not a/json/DataRequestsolution — so no newsolutionsbuilder. Only the example + feature test were missing.Testing
ruff check+ruff format --check: clean.