Skip to content

Commit 2058786

Browse files
update: remove outdated payment method examples and streamline README content
1 parent cc422d3 commit 2058786

File tree

1 file changed

+0
-80
lines changed

1 file changed

+0
-80
lines changed

README.md

Lines changed: 0 additions & 80 deletions
Original file line numberDiff line numberDiff line change
@@ -182,86 +182,6 @@ mutation doSepaPayment($cartId: String!, $returnUrl: String!) {
182182
}
183183
```
184184

185-
- Get the available payments methods with additional data for gateways:
186-
```graphql
187-
query {
188-
cart(cart_id: "{ CART_ID }") {
189-
available_payment_methods {
190-
code
191-
title
192-
buckaroo_additional {
193-
key
194-
values {
195-
name
196-
code
197-
img
198-
}
199-
value
200-
}
201-
}
202-
}
203-
}
204-
```
205-
206-
- Place order request example: In order to place a order you will need to the following 3 steps:
207-
- Set the payment method on the card with the required additional parameters using the default `setPaymentMethodOnCart` and the `buckaroo_additional` property
208-
- Set the return url using our custom migration `setBuckarooReturnUrl` required in order for the payment engine to redirect back to your application after the payment was completed/canceled/failed
209-
- Finally execute the the default `placeOrder` that will return a redirect url for the payment engine to complete the payment
210-
211-
For iDEAL we have the following example:
212-
```graphql
213-
mutation doBuckarooPayment(
214-
$cartId: String!
215-
$returnUrl: String!
216-
$methodCode: String!
217-
) {
218-
setPaymentMethodOnCart(
219-
input: {
220-
cart_id: $cartId
221-
payment_method: {
222-
code: $methodCode
223-
buckaroo_additional: { buckaroo_magento2_ideal: { issuer: "ABNANL2A" } }
224-
}
225-
}
226-
) {
227-
cart {
228-
items {
229-
product {
230-
name
231-
sku
232-
}
233-
}
234-
}
235-
}
236-
setBuckarooReturnUrl(input: { return_url: $returnUrl, cart_id: $cartId }) {
237-
success
238-
}
239-
placeOrder(input: { cart_id: $cartId }) {
240-
order {
241-
order_number
242-
buckaroo_additional {
243-
redirect
244-
transaction_id
245-
data {
246-
key
247-
value
248-
}
249-
}
250-
}
251-
}
252-
}
253-
254-
```
255-
After this migration is performed you will need to store the buckaroo `transaction_id` and redirect the user to complete the payment
256-
257-
In order to get the payment status after the user is redirected back we will use our custom migration `buckarooPaymentTransactionStatus` that will need the stored `transaction_id`
258-
259-
```graphql
260-
mutation buckarooPaymentTransactionStatus(input: { transaction_id: "E397CF4C24E64AA299F45246F9906F45" }) {
261-
payment_status,
262-
status_code
263-
}
264-
```
265185
### Additional information
266186
- **Support:** https://support.buckaroo.eu/contact
267187
- **Contact:** [support@buckaroo.nl](mailto:support@buckaroo.nl) or [+31 (0)30 711 50 50](tel:+310307115050)

0 commit comments

Comments
 (0)