Penny drop action node for graphs
What's new
Campaign, page, and segment-group graphs gain a fifth payment risk action node, RequirePennyDropNode. It lets the capture through, but billing must verify the card with a penny drop before the payment goes ahead.
The node carries only the usual node fields — id, x, y, title, description, next_node_id, break_on_error, and result — with id, x, and y required. It joins DeclinePaymentNode, Require3DSNode, BanUserNode, and BatchBanUserNode in the graph nodes discriminator and oneOf.
Impact
A fraud rule can now demand a card verification charge instead of choosing between a 3DS challenge and an outright decline, which suits cards and regions where 3DS isn't available.
Changes
| Resource | Change |
|---|---|
| create_campaign, update_campaign | Added RequirePennyDropNode to the graph.nodes discriminator and oneOf |
| get_campaign_graph, update_campaign_graph | Added the node to the graph nodes discriminator and oneOf |
| update_segment_group | Added the node to the graph.nodes discriminator and oneOf |
| get_pages, get_page, create_page, update_page, bulk_update_page, translate_page | Added the node to the DynamicBlock.graph_rules.nodes discriminator and oneOf |
Upgrade
- No action required. To use the node, add an entry to the graph nodes map with
model_typeset toRequirePennyDropNode. - Clients that validate graph responses against a generated model should regenerate, since this node type can now appear in
nodes.
도움이 필요하세요?
통합팀에 문의하십시오 [email protected]