Skip to content

[MKT_923]:feat/Relax required fields on POST /customer to match new checkout flow - #390

Merged
jaaaaavier merged 1 commit into
masterfrom
feat/update-params-for-checkout
Jul 21, 2026
Merged

[MKT_923]:feat/Relax required fields on POST /customer to match new checkout flow#390
jaaaaavier merged 1 commit into
masterfrom
feat/update-params-for-checkout

Conversation

@jaaaaavier

Copy link
Copy Markdown
Contributor

This PR Makes customerName, lineAddress1, lineAddress2, city and postalCode optional in the POST /customer body, keeping only country and captchaToken as required. The new checkout flow no longer collects full billing address up front for card payments, full address is only gathered for crypto payments. Matches the CreateCustomerPayload type already relaxed in @internxt/sdk@1.17.19.

@sonarqubecloud

Copy link
Copy Markdown

@sg-gs sg-gs left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM although I do not know if this affects any B2B-related payment, as those params are usually required or nice-to-have in that case.

@xabg2

xabg2 commented Jul 20, 2026

Copy link
Copy Markdown
Collaborator

LGTM although I do not know if this affects any B2B-related payment, as those params are usually required or nice-to-have in that case.

Afaik, b2b purchases are not supported anymore. At least I removed them from payments. Only supported "update/remove".

@jaaaaavier

Copy link
Copy Markdown
Contributor Author

All I can tell you is that when I spoke to Fran, he told me that if any company needed this, it would be done manually. I think it’s likely that it will be updated in the future.

@jaaaaavier
jaaaaavier merged commit 8257f15 into master Jul 21, 2026
10 of 11 checks passed
@jaaaaavier
jaaaaavier deleted the feat/update-params-for-checkout branch July 21, 2026 06:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants